Better Alignment of Flash Storage to Mobile System Behavior
summary
A lab of real Android phones and traced 24‑hour user sessions shows storage is idle most of the time — about 15 minutes busy per day — yet users still produce ~12 GB writes and ~74 GB reads; peak random IOPS hit ~2.5k IOPS while synthetic tests report 4k–11k but real workloads sit near 1–1.5k. Adding an SLC‑buffered mode with background copy and driver suspend delays prevents peak collapse (demo: 107 vs 27 MB/s sequential after buffer exhaustion). Patches to MMC drivers are under review.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:43Comparing to Synthetic Benchmarks
- 19:26Enable Backups
- 24:31Synthetic Benchmark
- 26:32User Activity
related talks
36mFrom Raw To Refined: The Evolution of Raw Flash Support in Linux
25mReducing Android Boot Times: Evaluating Proactive File Prefetching
29mPerformance Optimization on Xen-based Android Device
33mSSDFS: Flash-friendly File System with Highly Minimized GC Activity, Diff-on-write, & Deduplication
53mIntel ME: Flash File System Explained
46mMaximizing SD Card Life, Performance, and Monitoring with KrillKounter
30mScalable Parallel Flash Firmware for Many-core Architectures
38mEROFS, an Introduction and our Smartphone Practice