Making 768 servers look like 1
aarvin_roshin
22 points
3 comments
July 15, 2026
Related Discussions
Found 5 related stories in 99.6ms across 9,789 title embeddings via pgvector HNSW
- Making 768 servers look like 1 hisamafahri · 30 pts · July 16, 2026 · 100% similar
- Scaling to 1M concurrent sandboxes in seconds thundergolfer · 47 pts · July 16, 2026 · 55% similar
- 118M Queries per Second on Neki joshmgross · 89 pts · September 11, 2026 · 47% similar
- Dumb servers, smart clients: Distributing OS images with Quarry Levitating · 20 pts · September 30, 2026 · 47% similar
- It's Like Having 150 Extra Engineers glimshe · 36 pts · September 03, 2026 · 47% similar
Discussion Highlights (2 comments)
bddicken
Hey, I wrote this! Sharding is cool and foundational to making the internet work. I'm around to answer Qs.
elevation
Thanks for a well written article! When spec'ing a signle database host, I've been told to select the highest L1/L2 cache possible (allowing O(n^2) loads to complete with the least IO delay) with IOPs and RAM also being desirable. Does this hold when selecting hardware for shards? Do you ever see unusual ratios between egress bandwidth and shard count? For instance, do you ever see 128 shards under heavy load not managing to saturate a 1GbE link? Would love to see more of your writing on this topic.