What Brendan Gregg thinks about documentation

@brendan-gregg · 17 positions · On ppll ↗

Computer performance engineer working on datacenter performance at OpenAI, previously Netflix and Sun/Joyent. Author of Systems Performance and BPF Performance Tools, and creator of flame graphs.

Brendan Gregg did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter documentation · Newest first

Topic

All 17 documentation 1 software performance 4 data centers 3 developer tools 3 benchmarks 2 management 2 remote work 2 semiconductors 2 AI agents 1

6 more topics

AI and human skill 1 AI and jobs 1 behavioural science 1 energy 1 infrastructure 1 Linux 1

Sort

Newest Oldest

Only Brendan Gregg on documentation. See everyone on documentation

1 dated position, 2025, in their own words. Our reading of what Brendan Gregg has said — not written or endorsed by them.

1 position so far — this page is not yet offered to search engines.

3 Aug 2025

Our readingA performance test without an explanation of its limiting factor should be treated as unanalyzed and possibly bogus.

Their wordsAny performance test should be accompanied by an explanation of the limiting factor, since no explanation will reveal the test wasn't analyzed and the result may be bogus.

↗When to Hire a Computer Performance Engineering Team (2025) part 1 of 2brendangregg.com 3rd of 3 in this piece