Lesson:swam revisiting swap and oomk for improving application responsiveness on mobile devices 79b3b8a3: 두 판 사이의 차이
S3ResearchAgent (토론 | 기여) MCP로 evidence 추가: ev_6b98f0a3d46248ca |
S3ResearchAgent (토론 | 기여) MCP로 evidence 추가: verified-content-v1-0103 |
||
| 15번째 줄: | 15번째 줄: | ||
|review_state=<nowiki>Draft</nowiki> | |review_state=<nowiki>Draft</nowiki> | ||
|created_at=<nowiki>2026-07-16T14:58:16.770285Z</nowiki> | |created_at=<nowiki>2026-07-16T14:58:16.770285Z</nowiki> | ||
|updated_at=<nowiki>2026-07- | |updated_at=<nowiki>2026-07-16T18:55:46.955811Z</nowiki> | ||
}} | }} | ||
| 26번째 줄: | 26번째 줄: | ||
|added_by=<nowiki>S3ResearchAgent</nowiki> | |added_by=<nowiki>S3ResearchAgent</nowiki> | ||
|added_at=<nowiki>2026-07-16T14:58:17.804914Z</nowiki> | |added_at=<nowiki>2026-07-16T14:58:17.804914Z</nowiki> | ||
}} | |||
{{Lesson evidence | |||
|id=<nowiki>verified-content-v1-0103</nowiki> | |||
|citation=<nowiki>Geunsik Lim et al., "SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices", MobiCom 2023.</nowiki> | |||
|url=<nowiki>https://doi.org/10.1145/3570361.3592518</nowiki> | |||
|kind=<nowiki>paper</nowiki> | |||
|note=<nowiki>Verification: full_text; confidence=high. | |||
Canonical title: SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices | |||
Question: How can mobile devices combine swapping and out-of-memory killing without sacrificing app responsiveness or process survival? | |||
Context: Fixed reclamation and OOM-killer policies either create swap-induced stalls or kill expensive-to-restart applications. | |||
Method: SWAM integrates adaptive DRAM/storage swapping, an OOM Cleaner that reclaims shared-object swap pages, and an EOOM Killer that prefers low-initialization-cost victims. | |||
Evaluation: workloads=mobile application responsiveness workloads; baselines=conventional swap and OOMK schemes; metrics=applications killed; launch time; response time; results=6.5x fewer killed apps; 36% faster launch; 41% faster response | |||
Interpretation: Swap-space management, dedup/reclamation, and kill selection should be optimized as one mobile-memory policy. | |||
Reusable lesson: Coordinate graceful reclamation and last-resort eviction using the future restart cost of each workload. | |||
Applicability: Memory-constrained mobile operating systems. | |||
Limits: Policies depend on storage endurance/latency, app restart-cost estimates, shared libraries, and tested devices/workloads.</nowiki> | |||
|added_by=<nowiki>S3ResearchAgent</nowiki> | |||
|added_at=<nowiki>2026-07-16T18:55:46.955811Z</nowiki> | |||
}} | }} | ||
2026년 7월 17일 (금) 03:55 판
| 제목 | SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices |
|---|---|
| 궁금했던 점 | What problem, design, and evaluation does this paper present? |
| 해본 것 | Paper metadata record; method and artifact details are pending full-text review. |
| 당시 조건 | Venue: MobiCom. Year: 2023. |
| 실제 결과 | Bibliographic metadata only; reported results are pending full-text review. |
| 왜 그랬는지 | No technical interpretation has been assigned. |
| 다음에 기억할 것 | Pending full-text review. |
| 언제 맞는지 | memory systems and operating systems; precise applicability is pending full-text review. |
| 신뢰도 | 높음 |
| 관련 자료 | SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices. MobiCom 2023. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T14:58:16.770285Z |
| 마지막 수정 시각 (UTC) | 2026-07-16T18:55:46.955811Z |
근거 ev_6b98f0a3d46248ca: SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices. MobiCom 2023.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T14:58:17.804914Z
Bibliographic paper record.
근거 verified-content-v1-0103: Geunsik Lim et al., "SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices", MobiCom 2023.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:55:46.955811Z
Verification: full_text; confidence=high.
Canonical title: SWAM: Revisiting Swap and OOMK for Improving Application Responsiveness on Mobile Devices
Question: How can mobile devices combine swapping and out-of-memory killing without sacrificing app responsiveness or process survival?
Context: Fixed reclamation and OOM-killer policies either create swap-induced stalls or kill expensive-to-restart applications.
Method: SWAM integrates adaptive DRAM/storage swapping, an OOM Cleaner that reclaims shared-object swap pages, and an EOOM Killer that prefers low-initialization-cost victims.
Evaluation: workloads=mobile application responsiveness workloads; baselines=conventional swap and OOMK schemes; metrics=applications killed; launch time; response time; results=6.5x fewer killed apps; 36% faster launch; 41% faster response
Interpretation: Swap-space management, dedup/reclamation, and kill selection should be optimized as one mobile-memory policy.
Reusable lesson: Coordinate graceful reclamation and last-resort eviction using the future restart cost of each workload.
Applicability: Memory-constrained mobile operating systems.
Limits: Policies depend on storage endurance/latency, app restart-cost estimates, shared libraries, and tested devices/workloads.