# Uber Cuts Translation Cache Memory by up to 90% While Keeping P99 Latency Below 1 MS

Source: [InfoQ](https://www.infoq.com/news/2026/11/uber-go-translation-cache/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global) · 2026-11-20 · Cloud & DevOps
Page: https://themorning.dev/story/uber-cuts-translation-cache-memory-by-up-to-90-while-keeping-p99-latency-below-1-203ffa47448195c6
Kind: other · Impact: medium

## In brief

- Uber redesigned its Go-based translation cache to cut its initial memory footprint by more than 90%.
- The cache keeps a hit rate above 99.9% and p99 disk-backed cache miss latency below 100 microseconds.
- The hybrid architecture keeps in-memory keys and frequently accessed data, with the rest backed by disk.

## Why it matters

Teams running large in-memory caches can cut memory costs substantially with a hybrid memory and disk design while keeping tail latency low.

## Coverage

- [Uber Cuts Translation Cache Memory by up to 90% While Keeping P99 Latency Below 1 MS](https://www.infoq.com/news/2026/11/uber-go-translation-cache/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global) — InfoQ, 2026-11-20

Tags: go, caching, memory-optimization, latency, uber

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
