korrents
Nelson Elhage

What Nelson Elhage thinks about software performance

@nelson-elhage · 19 positions · On ppll ↗

Software engineer who writes the blog Made of Bugs about performance, debugging and understanding computer systems. Previously worked at Anthropic on interpretability, at Stripe on Sorbet, and at Ksplice.

Nelson Elhage 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.

6 dated positions, 2023 to 2025, in their own words. Our reading of what Nelson Elhage has said — not written or endorsed by them.

  1. My sense is that this hybrid is fairly common in practice; solvers aren't magical and if you can deduce additional structure using domain-specific analysis, it will often give the solver an important boost.

    ↗Solving regex crosswords with Z3blog.nelhage.com 1st of 2 in this piece

  2. 4 months earlier
  3. Modern CPUs mostly no longer struggle to predict the bytecode-dispatch indirect jump inside a "conventional" bytecode interpreter loop.

    ↗The ITTAGE indirect branch predictorblog.nelhage.com 1st of 3 in this piece

  4. most branches are heavily "biased" one way or another - e.g. a "branch taken" rate of 10% or 90% is more common than 50%

    ↗The ITTAGE indirect branch predictorblog.nelhage.com 2nd of 3 in this piece

  5. 4 months earlier
  6. compilers

    I'm hopeful this framework will turn out to be a much more robust style for writing performance-sensitive code, especially over time and as compilers evolve.

    ↗Performance of the Python 3.14 tail-call interpreterblog.nelhage.com 3rd of 3 in this piece

  7. 15 months earlier
  8. Profilers can only show you "what is there"; skillful performance engineering requires understanding the information that shapes and informs the profile but is "not there" in the profile itself.

    ↗Performance engineering, profilers, and seeing the invisibleblog.nelhage.com 1st of 2 in this piece

  9. a profile tells you how much time a program spent in a given operation; but not how much time it would spend if you optimized that operation.

    ↗Performance engineering, profilers, and seeing the invisibleblog.nelhage.com 2nd of 2 in this piece