CobbleDB vs DynamoDB: median batch-read latency 31.4ms→5.6ms, 20%+ cost savings
perplexity_ai · x · 2026-09-16
Perplexity shares production before/after numbers after replacing DynamoDB with CobbleDB: median batch-read latency fell from 31.4ms to 5.60ms and p99 from 123ms to 24.2ms, with internal cost models estimating at least 20% savings. Updates flow through Pillar (versioned state in YTsaurus) and Lorry (partitioned S3 batches), so replicas apply updates independently and recovering nodes don't delay others.
More from Infra
- clusyio's Portal lets Python jobs migrate to a new machine mid-run — AIFlow_ML · 2026-11-02
- Same intelligence gets 10x cheaper every 4-6 months, says Artificial Analysis — altryne · 2026-11-02
- tinybox owner: $11k-$22k local AI boxes beat buying GPUs outright — CedricMakes · 2026-11-02
- OpenAI plans to rebrand data centers as "AI compute campuses" after midterms — TorturedPoet30 · 2026-11-02
- Battery expert Maker_Matthew joins X, shows serialized batteries rolling off the line — yacineMTB · 2026-11-02
- Wan 2.2 color pulse fix and other hard-won tips from rendering a music video on one AMD GPU — wilppuse · 2026-11-02