Memory Management on Mobile Devices
summary
Evaluates Android Runtime garbage collection with a reproducible framework, curated 10 real Android apps benchmarked via UI Automator, and compares DaCapo plus a microbenchmark; implements a heap-size hijack via zygote specialization so individual apps run with controlled heaps without rebooting; measures empirical lower bounds on GC overheads and reports they range from 2% to 51% for modest heaps; finds semispace vs concurrent copying tradeoffs and shows some apps (Twitter) give chaotic results due to dynamic content.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04Motivation for mobile memory
- 3:49Android runtime challenges
- 5:14Measuring GC cost with ALOW
- 7:00Overcoming heap limits in Android
- 8:25Heap introspection issues
- 9:49Benchmark suite for Android apps
- 13:22Experimental setup
- 14:02Vanilla Java results
- 14:53Android app results incl. Twitter
- 16:30Conclusion
- 17:12Q&A
