Making the memory dump a powerful development tool
summary
Memory dumps get reworked into a compact, uploadable format called bmd that discards unused desktop-Java fields, hashes strings for privacy, and uses variable-length encodings inspired by protocol buffers. The implementation reduces a 210 MB HPROF to 3.8 MB bmd and further to 1.8 MB gzipped, claiming up to 97% size reduction versus HPROF. Libraries run conversion on-device slowly to avoid battery impact and convert back server-side for analysis with existing HPROF tools.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:42What is badoo?
- 1:44What is in a memory dump?
- 3:06Current use cases
- 4:14Why not more?
- 7:29Limitations of HPROF
- 9:58Better Memory Dumps
- 12:39Introducing BMD
- 15:58BMD vs HPROF
- 17:16Practical Applications
related talks
43mMemory Dumps: Going beyond the memory leak
47mTackling Memory Issues on the Instagram Android App
35mHow much memory do your objects really use?
07mAndroid memory tools and best practices
37mMemory Hotplug on Android
38mOptimize your app performance for the next generation of Android
34mThe Bytecode Mumbo Jumbo
32mRedex, Your Build, And You