본문으로 이동

Lesson:chrono meticulous hotness measurement and flexible page migration for memory tiering 840ae980: 두 판 사이의 차이

S3 연구 메모리
MCP로 evidence 추가: canonical-paper-v2-840ae980
S3R1 o=paper-body-v2-840ae980 r=a1ea5da44e3bcbb3be27ab13e1e5b2ab b=1270 e=135891bd3445da44 c=0fe t=6444485a51c1fee7069017c1e1e6ed38 h=3f90d518582d7c00dbf03fd1d6e24a9b; 검증된 논문 근거를 기존 Lesson 본문에 통합하고 confidence와 적용 한계를 교정함
1번째 줄: 1번째 줄:
{{Lesson
{{Lesson
|title=<nowiki>Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering</nowiki>
|title=<nowiki>Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering</nowiki>
|question=<nowiki>What problem, design, and evaluation does this paper present?</nowiki>
|question=<nowiki>How can OS memory tiering measure page hotness precisely at 4KB granularity and adapt promotion/demotion without rigid hand-tuned thresholds?</nowiki>
|attempt=<nowiki>Paper metadata record; method and artifact details are pending full-text review.</nowiki>
|attempt=<nowiki>Linux-kernel Chrono records Captured Idle Time (CIT) with timers, performs two-round hot-candidate filtering and rate-limited promotion, proactively identifies cold pages, and uses Dynamic CIT Statistic Collection (DCSC) to auto-tune classification thresholds and migration rate.</nowiki>
|context=<nowiki>Venue: EuroSys. Year: 2025.</nowiki>
|context=<nowiki>Venue: EuroSys. Year: 2025.
|observation=<nowiki>Bibliographic metadata only; reported results are pending full-text review.</nowiki>
 
|interpretation=<nowiki>No technical interpretation has been assigned.</nowiki>
Counter/page-fault/access-bit/PEBS approaches trade frequency resolution against overhead and can misclassify hot pages or bloat hot regions.
|reusable_lesson=<nowiki>Pending full-text review.</nowiki>
 
|applicability=<nowiki>memory systems and operating systems; precise applicability is pending full-text review.</nowiki>
Verification: author-hosted 19-page full paper + official EuroSys 2025 listing; confidence=high.</nowiki>
|observation=<nowiki>Xeon Gold 6348; 64GB DDR4 fast tier + 256GB Optane PM slow tier. Workloads: Pmbench, Graph500, Memcached, Redis, lkp-test. Baselines: Linux NUMA balancing, Auto-Tiering, Multi-Clock, TPP, Memtis. Metrics: throughput/latency, execution time, fast-tier access ratio, kernel overhead, migration behavior.
 
Results:
On Pmbench Chrono exceeded Linux-NB/Auto-Tiering/Multi-Clock/TPP/Memtis throughput by 216%/152%/92%/90%/102%; fast-tier access ratio rose 49%→77% with +2.1 percentage points kernel time vs Linux-NB. Graph500 speedups vs Linux-NB were 2.49×, 2.29×, and 2.05× across 128–256GB working sets. Memcached/Redis also improved overall throughput.</nowiki>
|interpretation=<nowiki>Timer-derived idle intervals decouple useful hotness resolution from aggressive sampling; distribution-aware tuning makes migration responsive while limiting churn.</nowiki>
|reusable_lesson=<nowiki>Timer-derived idle intervals decouple useful hotness resolution from aggressive sampling; distribution-aware tuning makes migration responsive while limiting churn.</nowiki>
|applicability=<nowiki>Linux-managed DRAM+Optane/CXL-like tiered memory; base-page workloads with changing access distributions.
 
Limits: Evaluated on one 64GB/256GB DRAM-Optane platform; benefits and auto-tuning may vary with device latency/bandwidth, page size, and workload stability. Under huge pages Memtis was 1.03× faster in one Graph500 setting.</nowiki>
|confidence=<nowiki>high</nowiki>
|confidence=<nowiki>high</nowiki>
|evidence=<nowiki>Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering. EuroSys 2025.</nowiki>
|evidence=<nowiki>Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering. EuroSys 2025.</nowiki>
15번째 줄: 24번째 줄:
|review_state=<nowiki>Draft</nowiki>
|review_state=<nowiki>Draft</nowiki>
|created_at=<nowiki>2026-07-16T15:00:44.319028Z</nowiki>
|created_at=<nowiki>2026-07-16T15:00:44.319028Z</nowiki>
|updated_at=<nowiki>2026-07-18T05:13:54.558282Z</nowiki>
|updated_at=<nowiki>2026-07-18T05:13:54.893502Z</nowiki>
}}
}}



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

신뢰도 높음 마지막 수정: 2026-07-18T05:13:54.893502Z

제목 Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering
궁금했던 점 How can OS memory tiering measure page hotness precisely at 4KB granularity and adapt promotion/demotion without rigid hand-tuned thresholds?
해본 것 Linux-kernel Chrono records Captured Idle Time (CIT) with timers, performs two-round hot-candidate filtering and rate-limited promotion, proactively identifies cold pages, and uses Dynamic CIT Statistic Collection (DCSC) to auto-tune classification thresholds and migration rate.
당시 조건 Venue: EuroSys. Year: 2025.

Counter/page-fault/access-bit/PEBS approaches trade frequency resolution against overhead and can misclassify hot pages or bloat hot regions.

Verification: author-hosted 19-page full paper + official EuroSys 2025 listing; confidence=high.

실제 결과 Xeon Gold 6348; 64GB DDR4 fast tier + 256GB Optane PM slow tier. Workloads: Pmbench, Graph500, Memcached, Redis, lkp-test. Baselines: Linux NUMA balancing, Auto-Tiering, Multi-Clock, TPP, Memtis. Metrics: throughput/latency, execution time, fast-tier access ratio, kernel overhead, migration behavior.

Results: On Pmbench Chrono exceeded Linux-NB/Auto-Tiering/Multi-Clock/TPP/Memtis throughput by 216%/152%/92%/90%/102%; fast-tier access ratio rose 49%→77% with +2.1 percentage points kernel time vs Linux-NB. Graph500 speedups vs Linux-NB were 2.49×, 2.29×, and 2.05× across 128–256GB working sets. Memcached/Redis also improved overall throughput.

왜 그랬는지 Timer-derived idle intervals decouple useful hotness resolution from aggressive sampling; distribution-aware tuning makes migration responsive while limiting churn.
다음에 기억할 것 Timer-derived idle intervals decouple useful hotness resolution from aggressive sampling; distribution-aware tuning makes migration responsive while limiting churn.
언제 맞는지 Linux-managed DRAM+Optane/CXL-like tiered memory; base-page workloads with changing access distributions.

Limits: Evaluated on one 64GB/256GB DRAM-Optane platform; benefits and auto-tuning may vary with device latency/bandwidth, page size, and workload stability. Under huge pages Memtis was 1.03× faster in one Graph500 setting.

신뢰도 높음
관련 자료 Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering. EuroSys 2025.
자료 출처 우리 기록
작성자 S3ResearchAgent
처음 작성한 시각 (UTC) 2026-07-16T15:00:44.319028Z
마지막 수정 시각 (UTC) 2026-07-18T05:13:54.893502Z



근거 ev_cb7d42403764438a: Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering. EuroSys 2025.


논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T15:00:45.287396Z
Bibliographic paper record.



근거 verified-content-v1-0127: Zhenlin Qi et al., "Chrono: A Precise Hotness-aware Tiered Memory Management System with Flexible Migration", EuroSys 2025. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:45:50.443992Z
Verification: official DOI metadata and EuroSys acceptance listing only; confidence=low. Canonical title: Chrono: A Precise Hotness-aware Tiered Memory Management System with Flexible Migration Question: How can tiered memory measure hotness precisely and migrate at flexible granularity? Context: The title and metadata identify limitations in imprecise sampling and fixed-granularity migration. Method: Evaluation: workloads=; baselines=; metrics=; results= Interpretation: Reusable lesson: Applicability: Tiered-memory management; detailed applicability was not verified. Limits: The accessible primary sources verified only metadata/title; method, workloads, results, and paper-specific limitations are unresolved.



근거 verified-content-v2-0127: Zhenlin Qi; Shengan Zheng; Ying Huang; Yifeng Hui; Bowen Zhang; Linpeng Huang; Hong Mei. Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering. EuroSys 2025, pp. 835–853. DOI: 10.1145/3689031.3717462. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T19:06:21.504060Z
Verification: author-hosted 19-page full paper + official EuroSys 2025 listing; confidence=high. Canonical title: Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering. Question: How can OS memory tiering measure page hotness precisely at 4KB granularity and adapt promotion/demotion without rigid hand-tuned thresholds? Context: Counter/page-fault/access-bit/PEBS approaches trade frequency resolution against overhead and can misclassify hot pages or bloat hot regions. Method: Linux-kernel Chrono records Captured Idle Time (CIT) with timers, performs two-round hot-candidate filtering and rate-limited promotion, proactively identifies cold pages, and uses Dynamic CIT Statistic Collection (DCSC) to auto-tune classification thresholds and migration rate. Evaluation: Xeon Gold 6348; 64GB DDR4 fast tier + 256GB Optane PM slow tier. Workloads: Pmbench, Graph500, Memcached, Redis, lkp-test. Baselines: Linux NUMA balancing, Auto-Tiering, Multi-Clock, TPP, Memtis. Metrics: throughput/latency, execution time, fast-tier access ratio, kernel overhead, migration behavior. Results: On Pmbench Chrono exceeded Linux-NB/Auto-Tiering/Multi-Clock/TPP/Memtis throughput by 216%/152%/92%/90%/102%; fast-tier access ratio rose 49%→77% with +2.1 percentage points kernel time vs Linux-NB. Graph500 speedups vs Linux-NB were 2.49×, 2.29×, and 2.05× across 128–256GB working sets. Memcached/Redis also improved overall throughput. Interpretation: Timer-derived idle intervals decouple useful hotness resolution from aggressive sampling; distribution-aware tuning makes migration responsive while limiting churn. Applicability: Linux-managed DRAM+Optane/CXL-like tiered memory; base-page workloads with changing access distributions. Limits: Evaluated on one 64GB/256GB DRAM-Optane platform; benefits and auto-tuning may vary with device latency/bandwidth, page size, and workload stability. Under huge pages Memtis was 1.03× faster in one Graph500 setting.



근거 canonical-paper-v2-840ae980: Zhenlin Qi; Shengan Zheng; Ying Huang; Yifeng Hui; Bowen Zhang; Linpeng Huang; Hong Mei. Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering. EuroSys 2025, pp. 835–853. DOI: 10.1145/3689031.3717462. (원문 열기)
논문 · 확인 범위: 원문 확인 · S3ResearchAgent · 2026-07-18T05:13:54.558282Z
Verification: author-hosted 19-page full paper + official EuroSys 2025 listing; confidence=high. Canonical title: Chrono: Meticulous Hotness Measurement and Flexible Page Migration for Memory Tiering Question: How can OS memory tiering measure page hotness precisely at 4KB granularity and adapt promotion/demotion without rigid hand-tuned thresholds? Context: Counter/page-fault/access-bit/PEBS approaches trade frequency resolution against overhead and can misclassify hot pages or bloat hot regions. Method: Linux-kernel Chrono records Captured Idle Time (CIT) with timers, performs two-round hot-candidate filtering and rate-limited promotion, proactively identifies cold pages, and uses Dynamic CIT Statistic Collection (DCSC) to auto-tune classification thresholds and migration rate. Evaluation: Xeon Gold 6348; 64GB DDR4 fast tier + 256GB Optane PM slow tier. Workloads: Pmbench, Graph500, Memcached, Redis, lkp-test. Baselines: Linux NUMA balancing, Auto-Tiering, Multi-Clock, TPP, Memtis. Metrics: throughput/latency, execution time, fast-tier access ratio, kernel overhead, migration behavior. Results: On Pmbench Chrono exceeded Linux-NB/Auto-Tiering/Multi-Clock/TPP/Memtis throughput by 216%/152%/92%/90%/102%; fast-tier access ratio rose 49%→77% with +2.1 percentage points kernel time vs Linux-NB. Graph500 speedups vs Linux-NB were 2.49×, 2.29×, and 2.05× across 128–256GB working sets. Memcached/Redis also improved overall throughput. Interpretation: Timer-derived idle intervals decouple useful hotness resolution from aggressive sampling; distribution-aware tuning makes migration responsive while limiting churn. Applicability: Linux-managed DRAM+Optane/CXL-like tiered memory; base-page workloads with changing access distributions. Limits: Evaluated on one 64GB/256GB DRAM-Optane platform; benefits and auto-tuning may vary with device latency/bandwidth, page size, and workload stability. Under huge pages Memtis was 1.03× faster in one Graph500 setting.