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.
saved by
related reading
- RLS sounds great until it isn't — PlanetScaleplanetscale.com
- Making 768 servers look like 1 — PlanetScaleplanetscale.com
- Everything I know about good system designseangoedecke.com
- The Ultimate Database Scaling Cheatsheet: Strategies for Optimizing Performance and Scalabilitydzone.com
- Benchmarking How Workflow Execution Scales on Postgres | DBOSdbos.dev
- Giovanni D'Antoniogiovannidantonio.com
- How to design resilient and large scale data systemsblog.dataengineer.io
- Database Sharding — PlanetScaleplanetscale.com
- Blog — PlanetScaleplanetscale.com
- Why benchmarking is hard | Epoch AIepoch.ai
- Nine ways to shoot yourself in the foot with PostgreSQLphilbooth.me
- Improve database performance with connection pooling - Stack Overflowstackoverflow.blog