✳flâneur — a map of the web's best reading
On benchmarking — PlanetScale
planetscale.com · 2,620 words · saved by 1 readers
Benchmarking is hard. Done wrong it is very misleading, and unfortunately it is frequently done wrong. Let's explore how not to make silly mistakes.
On benchmarking Ben Dicken [ @ BenjDicken ] | May 5, 2026 Benchmarking is hard. There are many ways to do it wrong and few to do it right. But zooming out from any single system or harness, there are broad principles that should be applied to all benchmarking. Using these correctly makes it difficult to produce biased results. Am I the world's best benchmarker? Certainly not. I invented the language balls , after all. But correctness and precision are important parts of PlanetScale's culture. We've spent considerable time learning the art of benchmarking, and are here to share best-practices.
Explore this link on the map →saved by
related reading
- Benchmarking How Workflow Execution Scales on Postgres | DBOSdbos.dev
- sled theoretical performance guide | sled-rs.github.iosled.rs
- sled theoretical performance guide | sled-rs.github.iosled.rs
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- Everything I know about good system designseangoedecke.com
- Why Percentiles Don’t Work the Way You Think - SolarWinds Blogorangematter.solarwinds.com
- Growth Benchmarks Are (Mostly) Useless - Brian Balfourbrianbalfour.com
- abseil / Performance Hintsabseil.io
- Databases are Fucking Stupid | Probably Danceprobablydance.com
- Scaling Temporal: The basics | Temporaltemporal.io
- Notes on Distributed Systems for Young Bloods – Something Similarsomethingsimilar.com
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com