Increasing throughput sometimes requires reducing parallelism. A look into why this is the case for Vitess + MySQL databases
Not long ago we watched a production MySQL database melt down for sixteen minutes.The errors started as a trickle, a handful per minute, then fed on themselves:minute errors/min queries/s
0 5 15,000 <- a burst of work arrives
10 1,400 1,500 <- error peak = throughput trough
16 0 2,500 <- locks released, backlog drained
18 0 8,500 <- full recovery, throughput jumps 5x
TL;DR: Black Friday on a 2M-product platform. Before adding a single server, EXPLAIN ANALYZE found...
They didn't know it was impossible, so they did it. — Mark Twain In the software industry, we've...
You've probably experienced this. Your app works perfectly during development. Then production...
I Fixed a 5s Database Bottleneck with CDC Dual-Writes We recently hit a critical...
Performance optimization isn't always about buying better hardware. Sometimes, it's about asking the...
A 'related articles' query matched 16,000 of 80,000 rows, sorted all of them by a computed expression, and returned six. How I…
When Servers Aren't the Problem: The Database Bottleneck
