Effectively Managing Memory At Gmail Scale
summary
Automatic GC is not enough; memory growth at Gmail scale produces measurable latency and millisecond GC pauses that break 16ms frames. Metrics come from periodic window.performance.memory samples (every 30 minutes) showing a huge 99th‑percentile footprint, and from live heap snapshots using the Chrome DevTools Heap Profiler and the object tracker. A demo cache of five messages reveals a leak: every third message keeps a DOM reference, preventing collection. Fixes shrink peak heaps and cut latency spikes.
AI-written summary · about
chapters (6)
related talks
53mPlugging Memory Leaks With The Chrome Dev Tools
21mMemory: Don't Forget to Take Out the Garbage
35mMemory Chronicles: Manage, Trace and Fix Memory Leaks
30mMemory Don't Forget To Take Out The Garbage
47mUntangling the web: Memory management in Chrome’s web platform implementation
23mWarp Speed Memory Management
20mMemory Leaks and the Havoc They Wreak
52mGC Tuning & Troubleshooting Crash Course