Tap a claim on the ring to put it at the centre.
← When diagnosing a performance problem, starting with a CPU profile is…
17 connected korrents · 14 moments from 18 Dec 2023 to 19 Sept 2026.
Everything filed under benchmarks
benchmarks
Everything filed under compilers
compilers
Everything filed under software performance
software performance
Everything filed under scaling laws
scaling laws
Everything filed under semiconductors
semiconductors
Everything filed under LLMs
LLMs
Everything filed under SQLite
SQLite Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Read this korrent: When diagnosing a performance problem, starting with a CPU profile is more useful than checking database queries first. When diagnosing a performance problem, starting with a CPU profile is more useful than checking database queries first. Last stated 2 months ago
21 Jul 2026
JE
Julia Evans — holds since 2026-07-21 — tap for who they are
Same subject: Model comparisons understate real progress, because benchmark tables do not control for how much test-time compute each answer used. — tap to centre the map on it Model comparisons understate real progress, because benchmark tables do not control for how much test-time compute each answer used. Last stated 3 months ago
26 Jun 2026
NB
Noam Brown — holds since 2026-06-26 — tap for who they are
Same subject: Profilers show where time is spent but not which of that time can feasibly be reduced or is worth optimizing. — tap to centre the map on it Profilers show where time is spent but not which of that time can feasibly be reduced or is worth optimizing. Last stated 3 years ago
18 Dec 2023
NE
Nelson Elhage — holds since 2023-12-18 — tap for who they are
Same subject: Hand-optimizing hot spots barely matters any more, because the libraries are already fast and CPUs are extremely good at running bad code quickly; what is left is architecture. — tap to centre the map on it Hand-optimizing hot spots barely matters any more, because the libraries are already fast and CPUs are extremely good at running bad code quickly; what is left is architecture. Last stated a month ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: CPU performance keeps improving quickly rather than stagnating. — tap to centre the map on it CPU performance keeps improving quickly rather than stagnating. Last stated 2 weeks ago
19 Sept 2026
DL
Daniel Lemire — holds since 2026-09-19 — tap for who they are
Same subject: Performance work used to mean half a day reading traces before writing a single fix, and language models have collapsed that step to minutes. — tap to centre the map on it Performance work used to mean half a day reading traces before writing a single fix, and language models have collapsed that step to minutes. Last stated a month ago
19 Aug 2026
AO
Addy Osmani — holds since 2026-08-19 — tap for who they are
Same subject: SQLite is a fine production database for a small site, but running it well is more complicated than the "SQLite in production is totally fine" blog posts make it sound. — tap to centre the map on it SQLite is a fine production database for a small site, but running it well is more complicated than the "SQLite in production is totally fine" blog posts make it sound. Last stated 3 months ago
17 Jul 2026
JE
Julia Evans — holds since 2026-07-17 — tap for who they are
Same subject: Synchronous database queries help avoid subtle bugs, because every await is a chance for the state of the world to change underneath the code. — tap to centre the map on it Synchronous database queries help avoid subtle bugs, because every await is a chance for the state of the world to change underneath the code. Last stated 2 years ago
26 Sept 2024
KV
Kenton Varda — holds since 2024-09-26 — tap for who they are
Same subject: "Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices. — tap to centre the map on it "Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices. Last stated a month ago
19 Aug 2026
AO
Addy Osmani — holds since 2026-08-19 — tap for who they are
Same subject: A benchmark result should be reported under a stated budget, or as a curve against test-time compute — never as a single number. — tap to centre the map on it A benchmark result should be reported under a stated budget, or as a curve against test-time compute — never as a single number. Last stated 3 months ago
26 Jun 2026
NB
Noam Brown — holds since 2026-06-26 — tap for who they are
Same subject: A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year. — tap to centre the map on it A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year. Last stated 4 weeks ago
3 Sept 2026
DR
Dax Raad — holds since 2026-09-03 — tap for who they are
Same subject: A carmaker's claim to be the safest is mostly an artefact of comparing a new car against a fleet average twelve years old. — tap to centre the map on it A carmaker's claim to be the safest is mostly an artefact of comparing a new car against a fleet average twelve years old. Last stated 3 years ago
19 Dec 2023
PK
Philip Koopman — holds since 2023-12-19 — tap for who they are
Same subject: A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach. — tap to centre the map on it A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. — tap to centre the map on it A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. Last stated 4 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle. — tap to centre the map on it A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: "Scaling" was powerful because it was one word: naming a research direction is what tells a whole field what to do next. — tap to centre the map on it "Scaling" was powerful because it was one word: naming a research direction is what tells a whole field what to do next. Last stated 10 months ago
25 Nov 2025
IS
Ilya Sutskever — holds since 2025-11-25 — tap for who they are
Same subject: A lab should spend most of its compute on research rather than on building the next model, because research is where the tenfold yearly efficiency gains come from. — tap to centre the map on it A lab should spend most of its compute on research rather than on building the next model, because research is where the tenfold yearly efficiency gains come from. Last stated 7 months ago
13 Mar 2026
DP
Dylan Patel — holds since 2026-03-13 — tap for who they are
Same subject: A model's capability is now a function of how much money you spend on it, so asking what a model can do means nothing until you name a budget. — tap to centre the map on it A model's capability is now a function of how much money you spend on it, so asking what a model can do means nothing until you name a budget. Last stated 3 months ago
26 Jun 2026
NB
Noam Brown — holds since 2026-06-26 — tap for who they are
At the centre
When diagnosing a performance problem, starting with a CPU profile is more useful than checking database queries first.
Holds Read this korrent →
Model comparisons understate real progress, because benchmark tables do not control for how much test-time compute each answer used.
Holds
Profilers show where time is spent but not which of that time can feasibly be reduced or is worth optimizing.
Holds
Hand-optimizing hot spots barely matters any more, because the libraries are already fast and CPUs are extremely good at running bad code quickly; what is left is architecture.
Holds
CPU performance keeps improving quickly rather than stagnating.
Holds
Performance work used to mean half a day reading traces before writing a single fix, and language models have collapsed that step to minutes.
Holds
SQLite is a fine production database for a small site, but running it well is more complicated than the "SQLite in production is totally fine" blog posts make it sound.
Holds
Synchronous database queries help avoid subtle bugs, because every await is a chance for the state of the world to change underneath the code.
Holds
"Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices.
Holds
A benchmark result should be reported under a stated budget, or as a curve against test-time compute — never as a single number.
Holds
A benchmark that ranks Claude Code last while it stays first in use is measuring the wrong thing, and has been for a year.
Holds
A carmaker's claim to be the safest is mostly an artefact of comparing a new car against a fleet average twelve years old.
Holds
A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach.
Holds
A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.
Holds
A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle.
Holds
"Scaling" was powerful because it was one word: naming a research direction is what tells a whole field what to do next.
Holds
A lab should spend most of its compute on research rather than on building the next model, because research is where the tenfold yearly efficiency gains come from.
Holds
A model's capability is now a function of how much money you spend on it, so asking what a model can do means nothing until you name a budget.
Holds