{"repo":"sderosiaux/performance-engineering-handbook","free":true,"listed":false,"github":"https://github.com/sderosiaux/performance-engineering-handbook","clone":"git clone https://github.com/sderosiaux/performance-engineering-handbook.git","description":"Full-stack performance engineering handbook — Linux kernel & eBPF, profiling/tracing, network & JVM/GPU tuning, storage engines, databases, distributed systems and streaming/ML data architectures, plus the high-performance data structures behind them: probabilistic sketches, vector/ANN indexes, columnar encoding, LSM & learned indexes, HFT C++.","language":null,"stars":22,"topics":["linux","ebpf","kernel-tuning","performance","profiling","algorithms","bloom-filter","columnar","data-structures","databases"],"license":null,"category":"analytics","readme_excerpt":"Performance Engineering Handbook Performance engineering, debugging, and tuning across the full stack: the Linux kernel and CPU microarchitecture, profiling and tracing, language runtimes, storage engines, databases, distributed systems, and the data structures that decide whether any of it is fast. It started as a Linux performance toolkit. It now spans 50 chapters and guides, from perf and eBPF up to vector indexes, LSM compaction, and HFT C++. The Linux chapters target kernel 6.6+ (EEVDF scheduler, modern eBPF). The data-structure, database, and architecture chapters are OS-agnostic. Last Updated: 2026-06 How to Use This Handbook 1. Start with the 60-second checklist (see Linux Quick Start) for quick triage 2. Use the Navigation below to find a topic, grouped into six parts 3. Check the cheatsheets for copy-paste commands 4. Refer to curated sources for deep dives on specific areas For investigation workflow: Before reaching for any tool , read 00b - Observability Boundaries. It encodes the single most important principle in this handbook: every layer's metrics lie by omission about the layer below it. A 99% PG buffer-hit ratio can coexist with a saturated NVMe; a JVM at 2 GB heap can be OOM-killed at 8 GB RSS; a container at 80% memory can be 50% reclaimable cache. If you skip this chapter, you will trust one layer and miss the truth in the next. Navigation Part I — Triage & Methodology Where to start, and how to not fool yourself. Chapter Description --------- ----------","default_branch":null,"files":null,"tree":[],"storefront":"/r/sderosiaux","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/sderosiaux/performance-engineering-handbook/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}