Tap a claim on the ring to put it at the centre.
← A network round trip is roughly a million times slower than a filesystem-cache read.
13 connected korrents · 12 moments from 4 Nov 2014 to 24 Sept 2026.
Everything filed under benchmarks
benchmarks
Everything filed under software performance
software performance
Everything filed under design
design
Everything filed under data centers
data centers 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: A network round trip is roughly a million times slower than a filesystem-cache read. A network round trip is roughly a million times slower than a filesystem-cache read. Last stated 2 months ago
15 Sept 2026
XI
Xe Iaso — holds since 2026-09-15 — tap for who they are
Same subject: Minimizing network round trips is essential to a good user experience, because bandwidth keeps improving and latency will not. — tap to centre the map on it Minimizing network round trips is essential to a good user experience, because bandwidth keeps improving and latency will not. Last stated 12 years ago
4 Nov 2014
GR
Guillermo Rauch — holds since 2014-11-04 — tap for who they are
Same subject: Starlink's latency is around 10ms, the same as or better than regular fiber internet, not the 1 second skeptics assume. — tap to centre the map on it Starlink's latency is around 10ms, the same as or better than regular fiber internet, not the 1 second skeptics assume. Last stated a month ago
24 Sept 2026
PL
Pieter Levels — holds since 2026-09-24 — tap for who they are
Same subject: A distributed system must assume there is no upper bound whatsoever on how long a message can take to cross the network. — tap to centre the map on it A distributed system must assume there is no upper bound whatsoever on how long a message can take to cross the network. Last stated 6 months ago
22 Apr 2026
MK
Martin Kleppmann — holds since 2026-04-22 — tap for who they are
Same subject: A server's real network throughput can exceed what its single fastest port suggests when a protocol supports channel bonding across multiple links. — tap to centre the map on it A server's real network throughput can exceed what its single fastest port suggests when a protocol supports channel bonding across multiple links. Last stated 2 months ago
23 Aug 2026
SH
Scott Hanselman — holds since 2026-08-23 — tap for who they are
Same subject: A performance test without an explanation of its limiting factor should be treated as unanalyzed and possibly bogus. — tap to centre the map on it A performance test without an explanation of its limiting factor should be treated as unanalyzed and possibly bogus. Last stated a year ago
3 Aug 2025
BG
Brendan Gregg — holds since 2025-08-03 — tap for who they are
Same subject: Performance test results are highly dependent on the specific machine, library versions, and other components used, making them hard to compare over time. — tap to centre the map on it Performance test results are highly dependent on the specific machine, library versions, and other components used, making them hard to compare over time. Last stated 3 months ago
14 Aug 2026
DS
Daniel Stenberg — holds since 2026-08-14 — tap for who they are
Same subject: 'Everyone gets it wrong sometimes' is a bad argument when assessing track records. — tap to centre the map on it 'Everyone gets it wrong sometimes' is a bad argument when assessing track records. Last stated 3 months ago
2 Aug 2026
AK
Adam Kucharski — holds since 2026-08-02 — 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 3 months ago
19 Aug 2026
AO
Addy Osmani — holds since 2026-08-19 — tap for who they are
Same subject: "Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove. — tap to centre the map on it "Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen. — tap to centre the map on it A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — 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 4 months ago
26 Jun 2026
NB
Noam Brown — holds since 2026-06-26 — 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 4 months ago
26 Jun 2026
NB
Noam Brown — holds since 2026-06-26 — tap for who they are
Same subject: Language models perform better on benchmark problems released before their training data cutoff, indicating data contamination inflates scores. — tap to centre the map on it Language models perform better on benchmark problems released before their training data cutoff, indicating data contamination inflates scores. Last stated 2 years ago
13 May 2024
SR
Sebastian Ruder — holds since 2024-05-13 — tap for who they are
At the centre
A network round trip is roughly a million times slower than a filesystem-cache read.
Holds Read this korrent →
Minimizing network round trips is essential to a good user experience, because bandwidth keeps improving and latency will not.
Holds
Starlink's latency is around 10ms, the same as or better than regular fiber internet, not the 1 second skeptics assume.
Holds
A distributed system must assume there is no upper bound whatsoever on how long a message can take to cross the network.
Holds
A server's real network throughput can exceed what its single fastest port suggests when a protocol supports channel bonding across multiple links.
Holds
A performance test without an explanation of its limiting factor should be treated as unanalyzed and possibly bogus.
Holds
Performance test results are highly dependent on the specific machine, library versions, and other components used, making them hard to compare over time.
Holds
'Everyone gets it wrong sometimes' is a bad argument when assessing track records.
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
"Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove.
Holds
A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen.
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 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
Language models perform better on benchmark problems released before their training data cutoff, indicating data contamination inflates scores.
Holds