Book · 2013
Systems Performance: Enterprise and the Cloud
by Brendan Gregg
Brendan Gregg's 800-page field manual for diagnosing CPU, memory, disk, and network bottlenecks on Linux and cloud systems.
What does Reddit think of Systems Performance: Enterprise and the Cloud?
Fourteen mentions across r/devops, r/ExperiencedDevs, and r/programming over seven years, and the pattern is consistent: this book appears in curated reading lists alongside W. Richard Stevens and TLPI, never as a standalone recommendation. The ↑86 thread puts it next to Advanced Programming in the UNIX Environment as material Facebook Production Engineering handed out in 2014. That's the real comp: this is a peer of Stevens, not a replacement for it. r/ExperiencedDevs treats it differently. The ↑19 thread calls it essential for diagnosing and understanding system behavior; the ↑16 thread brackets it with BPF Performance Tools as simply "any Brendan Gregg book (perf 101)". Nobody on Reddit fights about whether to use a flame graph.
Community feedback & reader fit
Themes
- · Linux systems performance methodology
- · CPU, memory, disk, and network profiling
- · BPF and flame graphs
- · Cloud and enterprise production environments
- · OS internals as a performance foundation
Common praise
- + The methodology chapters give you a structured way to approach a slow system instead of guessing at knobs.
- + r/ExperiencedDevs (↑19) cites it as the go-to reference for diagnosing and understanding system behavior in production.
- + Facebook Production Engineering handed it out as onboarding reading — that's a stronger endorsement than a five-star review.
- + The flame graph tooling introduced here became standard enough that most teams now use it without knowing where it came from.
Common criticism
- − At 800+ pages it's a reference book, not a tutorial — reading cover to cover is not how it works.
- − The 2013 first edition aged around cloud-native tooling; the second edition updates this but doesn't fully close the gap.
- − Reddit never mentions it in isolation — it always appears in lists, which means it's a component, not a foundation.
Who it's for
You're a mid-to-senior engineer who's been handed a slow service and told to fix it. You know the stack but not the methodology. This book is the methodology. If you're preparing for production engineering roles at FAANG — the r/devops thread (↑86) makes clear this is what they expect you to have read. Skip it if you want a step-by-step tutorial; come back when you need a reference that tells you exactly which tool to run and what the output means.
Mentions over time
Top subreddits
Which Reddit comments matter for Systems Performance: Enterprise and the Cloud?
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“I am currently in the process of preparing for FAANG interviews with 4 YoE. Instead of doing side projects I simply bit the bullet and started learning these foundational technologies and concepts. I hope that my resume speaks for itself and I can impress with my strong basics. Books I can recommend…
“These are the ones that Facebook Production Engineering gave me in 2014 after I accepted. There isn't that much of a difference in terms of interviews. W. Richard Stevens - Advanced Programming in the UNIX Environment Mike Gancarz - Linux and the Unix Philosophy Eric S. Raymond - Art of UN…
“If you've not read it; this is a good book: ​ Some examples that spring to mind: Task was to try and increase performan…
“I'm going to be blunt here, don't take it personal Yeah Im a hiring manager and looked at it how I look at resumes "for real" and I would have moved on very quickly. For one, while I'd love to hire junior employees in a remote work environment it's very difficult and ends up taking up a lot of the…
“Great write-up. On a side note, I have found the book "Systems Performance: Enterprise and the Cloud" by Brendan Gregg extremely useful for tuning the Performance.
“I would add to this: 1. Linux Kernel Development - Robert Love: while you may not necessarily need to know kernel programming, it’s a good overview of the kernel internals and makes you think deeper about the code you write. 2. Systems Performance by Brendan Gregg - fantastic book to diagnose and u…
“It was! My top 5 would be something like: * Operating Systems: Three Easy Pieces (os 101) * The Algorithm Design Manual (concise algorithms reference) * The Linux Programming Interface (syscalls 101) * BPF Performance Tools / Systems Performance - basically any Brendan Gregg book (perf 101) * Desi…
“I personally prefer these books: Ansible for DevOps, Jeff Geerling Ansile for AWS, Jeff Geerling Ansible for Kubernetes, Jeff Geerling [ht…
Convinced? Pick up Systems Performance: Enterprise and the Cloud
What else does r/devops read?
Other books mentioned in the same sub, ranked. Shared-sub overlap with this title breaks ties.
The Phoenix Project
Gene Kim
An IT manager inherits a failing project, a mutinous ops team, and a CEO deadline — and has to ship before the company does.
The DevOps Handbook
Gene Kim
Four practitioners codify how Etsy, Netflix, and Google actually ship software — then explain why your org does the opposite.
The Unicorn Project
Gene Kim
The Phoenix Project retold from the developer's chair: same burning company, different seat at the fire.
Continuous Delivery
Jez Humble
The 2010 Humble-Farley textbook that turned "ship when it's done" into a measurable engineering discipline with pipelines, gates, and deployment rings.
Accelerate
Nicole Forsgren
Nicole Forsgren's research team ran the numbers on software delivery and found that deployment frequency and stability move together, not against each other.
Designing Data-Intensive Applications
Martin Kleppmann
A backend engineer's field guide to the tradeoffs behind every database, queue, and distributed system you will ever touch.
Systems Performance: Enterprise and the Cloud — frequently asked
Is Systems Performance worth reading if I'm not a performance engineer?+
Depends on your seniority. r/ExperiencedDevs consistently pairs it with OS internals books like TLPI as foundational reading for senior engineers. If you regularly touch production systems, yes. If you're writing application code and never look at flame graphs, the ROI is low — but the r/devops thread (↑86) suggests FAANG expects you to have covered it regardless.
What does Reddit actually say about Systems Performance by Brendan Gregg?+
The ↑86 and ↑38 r/devops threads frame it as production engineering onboarding material rather than an optional read.
Should I read Systems Performance or BPF Performance Tools first?+
Systems Performance first. The r/ExperiencedDevs ↑16 thread treats them as interchangeable — 'basically any Brendan Gregg book (perf 101)' — but Systems Performance covers the methodology that makes the BPF tooling legible. BPF Performance Tools assumes you already know what question you're trying to answer.
Is Systems Performance still relevant for cloud environments in 2026?+
Yes, with caveats. The 2020 second edition added cloud and container coverage, and r/devops mentions run through 2025. The Linux performance methodology doesn't expire just because workloads moved to Kubernetes. The specific tooling chapters age faster than the methodology chapters — read those accordingly.