Reproduce “SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices” on OpenResearch
Turn your favorite coding agents into research agents that review literature, develop hypotheses, and run experiments.
Universal app for Apple silicon and Intel. Requires macOS 11 or later.
About this paper
Geunsik Lim, Donghyun Kang, MyungJoo Ham, Young Ik Eom
SWAM combines adaptive swapping, swap-space cleaning, and launch-cost-aware process termination to preserve Android application responsiveness under sustained memory pressure. Across four-week experiments on a Pixel 6 and an emulated low-memory configuration, it improved launch time by up to 38%, reduced average response time by up to 44%, and cut OOMK-triggered application kills by as much as 6.5×.
Key insights
- Native shared-object pages are an important reclamation target: most examined shared-object pages were not shared across applications, allowing many to be moved or discarded with limited system-wide impact.
- Swap and killing have complementary costs, so a policy that dynamically combines page-level reclamation with application-aware termination can better optimize perceived responsiveness than either mechanism alone.
- Application launch behavior provides useful signals for memory management; symbol lookup and XML layout processing can estimate which processes are more expensive to relaunch.
Summary by alphaXiv.
Tip: change arxiv.org to autoarxiv.org in any arXiv abstract link to open the paper here.