Lesson:pmr fast application response via parallel memory reclaim on mobile devices 4c59e491
| 제목 | PMR: Fast Application Response via Parallel Memory Reclaim on Mobile Devices |
|---|---|
| 궁금했던 점 | How can mobile memory reclamation avoid foreground stalls caused by shrinking and dirty-page writeback? |
| 해본 것 | PMR proactively shrinks pages, decouples shrink from writeback, and batches unmapping/writeback in storage-friendly form. |
| 당시 조건 | Venue: USENIX ATC. Year: 2025.
Reactive Android reclamation couples page shrinking with storage work on the latency-critical path. Verification: official USENIX page and abstract; confidence=high. |
| 실제 결과 | workloads=applications on real mobile devices; baselines=Android memory reclamation; metrics=response time; results=up to 43.6% improvement |
| 왜 그랬는지 | Reclamation latency falls when dirty work is predicted, separated, and shaped for the storage device. |
| 다음에 기억할 것 | Move reclaim preparation off the demand path and batch device-facing cleanup. |
| 언제 맞는지 | Memory-constrained mobile systems with flash-backed swapping/writeback.
Limits: Reported evaluation is mobile/Android-specific; energy and flash-wear effects were not in the accessible abstract. |
| 신뢰도 | 중간 |
| 관련 자료 | PMR: Fast Application Response via Parallel Memory Reclaim on Mobile Devices. USENIX ATC 2025. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T14:59:19.191176Z |
| 마지막 수정 시각 (UTC) | 2026-07-18T14:58:55.793567Z |
근거 ev_e546e051c775482b: PMR: Fast Application Response via Parallel Memory Reclaim on Mobile Devices. USENIX ATC 2025.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T14:59:20.214703Z
Bibliographic paper record.
근거 verified-content-v1-0120: Wentong Li et al., "PMR: Proactive Memory Reclamation for Mobile Devices", USENIX ATC 2025.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:45:09.394643Z
Verification: official USENIX page and abstract; confidence=high.
Canonical title: PMR: Proactive Memory Reclamation for Mobile Devices
Question: How can mobile memory reclamation avoid foreground stalls caused by shrinking and dirty-page writeback?
Context: Reactive Android reclamation couples page shrinking with storage work on the latency-critical path.
Method: PMR proactively shrinks pages, decouples shrink from writeback, and batches unmapping/writeback in storage-friendly form.
Evaluation: workloads=applications on real mobile devices; baselines=Android memory reclamation; metrics=response time; results=up to 43.6% improvement
Interpretation: Reclamation latency falls when dirty work is predicted, separated, and shaped for the storage device.
Reusable lesson: Move reclaim preparation off the demand path and batch device-facing cleanup.
Applicability: Memory-constrained mobile systems with flash-backed swapping/writeback.
Limits: Reported evaluation is mobile/Android-specific; energy and flash-wear effects were not in the accessible abstract.
근거 canonical-paper-v2-4c59e491: Wentong Li et al., "PMR: Fast Application Response via Parallel Memory Reclaim on Mobile Devices", USENIX ATC 2025.
(원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:34:08.884132Z
Verification: official USENIX page and abstract; confidence=medium.
Canonical title: PMR: Fast Application Response via Parallel Memory Reclaim on Mobile Devices
Question: How can mobile memory reclamation avoid foreground stalls caused by shrinking and dirty-page writeback?
Context: Reactive Android reclamation couples page shrinking with storage work on the latency-critical path.
Method: PMR proactively shrinks pages, decouples shrink from writeback, and batches unmapping/writeback in storage-friendly form.
Evaluation: workloads=applications on real mobile devices; baselines=Android memory reclamation; metrics=response time; results=up to 43.6% improvement
Interpretation: Reclamation latency falls when dirty work is predicted, separated, and shaped for the storage device.
Reusable lesson: Move reclaim preparation off the demand path and batch device-facing cleanup.
Applicability: Memory-constrained mobile systems with flash-backed swapping/writeback.
Limits: Reported evaluation is mobile/Android-specific; energy and flash-wear effects were not in the accessible abstract.
자료 검증 verify_36d6d4f5119dad765290:
ev_e546e051c775482b ·
판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:54.911756Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=a081b6e1c89ece7991edca19181a392b8a5ce26be78218f93b0ee2028f5b9a12 / 위치: 보존 파일 objects/sha256/a0/a081b6e1c89ece7991edca19181a392b8a5ce26be78218f93b0ee2028f5b9a12
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.
자료 검증 verify_d737b28e714dd35e584e:
verified-content-v1-0120 ·
판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:55.246142Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=a081b6e1c89ece7991edca19181a392b8a5ce26be78218f93b0ee2028f5b9a12 / 위치: 보존 파일 objects/sha256/a0/a081b6e1c89ece7991edca19181a392b8a5ce26be78218f93b0ee2028f5b9a12
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.
자료 검증 verify_73195028418d135b3541:
canonical-paper-v2-4c59e491 ·
판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:55.793567Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=a081b6e1c89ece7991edca19181a392b8a5ce26be78218f93b0ee2028f5b9a12 / 위치: 보존 파일 objects/sha256/a0/a081b6e1c89ece7991edca19181a392b8a5ce26be78218f93b0ee2028f5b9a12
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.