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.

Related event: Perplexity's CobbleDB Cuts Median Batch-Read Latency to 5.6ms, Saving 20%(2 posts)→

Original post →

More from Infra

Infra channel →