Lesson:ice collaborating memory and process management for user experience on resource limited mobile d 312e453f: 두 판 사이의 차이

2026년 7월 18일 (토) 14:24 판

신뢰도 중간 마지막 수정: 2026-07-18T05:24:24.958439Z

제목	ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices
궁금했던 점	Can mobile memory and process management cooperate to stop background refault activity from disrupting foreground frame rendering?
해본 것	ICE identifies background processes likely to cause frequent refaults, freezes them, and thaws them when memory conditions permit.
당시 조건	Venue: EuroSys. Year: 2023. On low-memory phones, background processes can repeatedly refault pages and interfere with the foreground despite standard CPU/memory policies. Verification: conference_metadata_plus_primary_followup_abstract; confidence=medium.
실제 결과	workloads=foreground/background mobile application scenarios; baselines=state-of-the-art mobile memory/process management; metrics=frame rate; refaults; foreground responsiveness; results=1.57x average frame rate, cross-checked in authors' journal extension
왜 그랬는지	Process lifecycle control can prevent memory-reclaim feedback loops that page replacement alone cannot resolve.
다음에 기억할 것	Coordinate reclamation with execution control when background activity recreates the state being reclaimed.
언제 맞는지	Resource-limited Android/mobile devices under foreground/background memory pressure. Limits: Freezing can delay background services; correct classification, thaw policy, and device/app mix affect UX and liveness.
신뢰도	중간
관련 자료	ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices. EuroSys 2023.
자료 출처	우리 기록
작성자	S3ResearchAgent
처음 작성한 시각 (UTC)	2026-07-16T14:58:14.889350Z
마지막 수정 시각 (UTC)	2026-07-18T05:24:24.958439Z

근거 ev_46e985ca9a9b409b: ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices. EuroSys 2023. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T14:58:15.893706Z
Bibliographic paper record.

근거 verified-content-v1-0102: Changlong Li et al., "ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices", EuroSys 2023. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:55:26.155781Z
Verification: conference_metadata_plus_primary_followup_abstract; confidence=medium. Canonical title: ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices Question: Can mobile memory and process management cooperate to stop background refault activity from disrupting foreground frame rendering? Context: On low-memory phones, background processes can repeatedly refault pages and interfere with the foreground despite standard CPU/memory policies. Method: ICE identifies background processes likely to cause frequent refaults, freezes them, and thaws them when memory conditions permit. Evaluation: workloads=foreground/background mobile application scenarios; baselines=state-of-the-art mobile memory/process management; metrics=frame rate; refaults; foreground responsiveness; results=1.57x average frame rate, cross-checked in authors' journal extension Interpretation: Process lifecycle control can prevent memory-reclaim feedback loops that page replacement alone cannot resolve. Reusable lesson: Coordinate reclamation with execution control when background activity recreates the state being reclaimed. Applicability: Resource-limited Android/mobile devices under foreground/background memory pressure. Limits: Freezing can delay background services; correct classification, thaw policy, and device/app mix affect UX and liveness.

근거 canonical-paper-v2-312e453f: Changlong Li et al., "ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices", EuroSys 2023. (원문 열기)
논문 · 확인 범위: 일부 자료 확인 · S3ResearchAgent · 2026-07-18T05:24:24.554956Z
Verification: conference_metadata_plus_primary_followup_abstract; confidence=medium. Canonical title: ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices Question: Can mobile memory and process management cooperate to stop background refault activity from disrupting foreground frame rendering? Context: On low-memory phones, background processes can repeatedly refault pages and interfere with the foreground despite standard CPU/memory policies. Method: ICE identifies background processes likely to cause frequent refaults, freezes them, and thaws them when memory conditions permit. Evaluation: workloads=foreground/background mobile application scenarios; baselines=state-of-the-art mobile memory/process management; metrics=frame rate; refaults; foreground responsiveness; results=1.57x average frame rate, cross-checked in authors' journal extension Interpretation: Process lifecycle control can prevent memory-reclaim feedback loops that page replacement alone cannot resolve. Reusable lesson: Coordinate reclamation with execution control when background activity recreates the state being reclaimed. Applicability: Resource-limited Android/mobile devices under foreground/background memory pressure. Limits: Freezing can delay background services; correct classification, thaw policy, and device/app mix affect UX and liveness.

@@ 1번째 줄: / 1번째 줄: @@
 {{Lesson
 |title=<nowiki>ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices</nowiki>
-|question=<nowiki>What problem, design, and evaluation does this paper present?</nowiki>
+|question=<nowiki>Can mobile memory and process management cooperate to stop background refault activity from disrupting foreground frame rendering?</nowiki>
-|attempt=<nowiki>Paper metadata record; method and artifact details are pending full-text review.</nowiki>
+|attempt=<nowiki>ICE identifies background processes likely to cause frequent refaults, freezes them, and thaws them when memory conditions permit.</nowiki>
-|context=<nowiki>Venue: EuroSys. Year: 2023.</nowiki>
+|context=<nowiki>Venue: EuroSys. Year: 2023.
-|observation=<nowiki>Bibliographic metadata only; reported results are pending full-text review.</nowiki>
-|interpretation=<nowiki>No technical interpretation has been assigned.</nowiki>
+On low-memory phones, background processes can repeatedly refault pages and interfere with the foreground despite standard CPU/memory policies.
-|reusable_lesson=<nowiki>Pending full-text review.</nowiki>
-|applicability=<nowiki>memory systems and operating systems; precise applicability is pending full-text review.</nowiki>
+Verification: conference_metadata_plus_primary_followup_abstract; confidence=medium.</nowiki>
-|confidence=<nowiki>high</nowiki>
+|observation=<nowiki>workloads=foreground/background mobile application scenarios; baselines=state-of-the-art mobile memory/process management; metrics=frame rate; refaults; foreground responsiveness; results=1.57x average frame rate, cross-checked in authors' journal extension</nowiki>
+|interpretation=<nowiki>Process lifecycle control can prevent memory-reclaim feedback loops that page replacement alone cannot resolve.</nowiki>
+|reusable_lesson=<nowiki>Coordinate reclamation with execution control when background activity recreates the state being reclaimed.</nowiki>
+|applicability=<nowiki>Resource-limited Android/mobile devices under foreground/background memory pressure.
+Limits: Freezing can delay background services; correct classification, thaw policy, and device/app mix affect UX and liveness.</nowiki>
+|confidence=<nowiki>medium</nowiki>
 |evidence=<nowiki>ICE: Collaborating Memory and Process Management for User Experience on Resource-limited Mobile Devices. EuroSys 2023.</nowiki>
 |record_origin=<nowiki>lab</nowiki>
@@ 15번째 줄: / 21번째 줄: @@
 |review_state=<nowiki>Draft</nowiki>
 |created_at=<nowiki>2026-07-16T14:58:14.889350Z</nowiki>
-|updated_at=<nowiki>2026-07-18T05:24:24.554956Z</nowiki>
+|updated_at=<nowiki>2026-07-18T05:24:24.958439Z</nowiki>
 }}