본문으로 이동

Lesson:telescope telemetry for gargantuan memory footprint applications 6a766ffb: 두 판 사이의 차이

S3 연구 메모리
MCP로 evidence 추가: verified-content-v1-0067
S3V1 o=s3rm-remediate-v1:9d69fb78961fa55e0d00658da3920d87438896a00b91 r=9ec222e75e9c0be6b239d00beb3a1c40 b=2591 e=2597ef6119a9657c8c5baefa45cbe9e7292eaae503c333258502bef6d967fe62 t=4d5be93997f8d5de658f61156de2c666 h=a4e3a6e95b2f7049f4954814a45c77f1
 
(같은 사용자의 중간 판 4개는 보이지 않습니다)
1번째 줄: 1번째 줄:
{{Lesson
{{Lesson
|title=<nowiki>Telescope: Telemetry for Gargantuan Memory Footprint Applications</nowiki>
|title=<nowiki>Telescope: Telemetry for Gargantuan Memory Footprint Applications</nowiki>
|question=<nowiki>What problem, design, and evaluation does this paper present?</nowiki>
|question=<nowiki>How can systems identify hot and cold memory regions at terabyte-to-petabyte scale with little CPU cost?</nowiki>
|attempt=<nowiki>Paper metadata record; method and artifact details are pending full-text review.</nowiki>
|attempt=<nowiki>Telescope profiles upper page-table levels to identify coarse hot/cold subtrees and selectively refine them.</nowiki>
|context=<nowiki>Venue: USENIX ATC. Year: 2024.</nowiki>
|context=<nowiki>Venue: USENIX ATC. Year: 2024.
|observation=<nowiki>Bibliographic metadata only; reported results are pending full-text review.</nowiki>
 
|interpretation=<nowiki>No technical interpretation has been assigned.</nowiki>
Per-page sampling becomes too expensive and slow as memory footprints grow.
|reusable_lesson=<nowiki>Pending full-text review.</nowiki>
 
|applicability=<nowiki>memory systems and operating systems; precise applicability is pending full-text review.</nowiki>
Verification: official_abstract; confidence=high.</nowiki>
|confidence=<nowiki>high</nowiki>
|observation=<nowiki>workloads=5 TB microbenchmark; 1–2 TB real benchmarks; baselines=state-of-the-art memory telemetry; metrics=precision; recall; CPU overhead; throughput; results=&gt;90% precision and recall at 0.9% of one CPU; 5.6–34% throughput improvement</nowiki>
|interpretation=<nowiki>Hierarchical address-translation metadata provides scalable aggregation before expensive fine-grained inspection.</nowiki>
|reusable_lesson=<nowiki>Use hierarchy to prune monitoring work at extreme scale.</nowiki>
|applicability=<nowiki>Tiering and telemetry for very large-memory applications.
 
Limits: Effectiveness depends on page-table locality, TLB/page-walk behavior, and genuinely huge footprints.</nowiki>
|confidence=<nowiki>medium</nowiki>
|evidence=<nowiki>Telescope: Telemetry for Gargantuan Memory Footprint Applications. USENIX ATC 2024.</nowiki>
|evidence=<nowiki>Telescope: Telemetry for Gargantuan Memory Footprint Applications. USENIX ATC 2024.</nowiki>
|record_origin=<nowiki>lab</nowiki>
|record_origin=<nowiki>lab</nowiki>
15번째 줄: 21번째 줄:
|review_state=<nowiki>Draft</nowiki>
|review_state=<nowiki>Draft</nowiki>
|created_at=<nowiki>2026-07-16T14:56:51.302828Z</nowiki>
|created_at=<nowiki>2026-07-16T14:56:51.302828Z</nowiki>
|updated_at=<nowiki>2026-07-16T18:43:02.334604Z</nowiki>
|updated_at=<nowiki>2026-07-18T15:00:41.738198Z</nowiki>
}}
}}


44번째 줄: 50번째 줄:
|added_by=<nowiki>S3ResearchAgent</nowiki>
|added_by=<nowiki>S3ResearchAgent</nowiki>
|added_at=<nowiki>2026-07-16T18:43:02.334604Z</nowiki>
|added_at=<nowiki>2026-07-16T18:43:02.334604Z</nowiki>
}}
{{Lesson evidence
|id=<nowiki>canonical-paper-v2-6a766ffb</nowiki>
|citation=<nowiki>Alan Nair et al., "Telescope: Telemetry for Gargantuan Memory Footprint Applications", USENIX ATC 2024.</nowiki>
|url=<nowiki>https://www.usenix.org/conference/atc24/presentation/nair</nowiki>
|kind=<nowiki>paper</nowiki>
|verification_basis=<nowiki>official_abstract</nowiki>
|note=<nowiki>Verification: official_abstract; confidence=medium.
Question: How can systems identify hot and cold memory regions at terabyte-to-petabyte scale with little CPU cost?
Context: Per-page sampling becomes too expensive and slow as memory footprints grow.
Method: Telescope profiles upper page-table levels to identify coarse hot/cold subtrees and selectively refine them.
Evaluation: workloads=5 TB microbenchmark; 1–2 TB real benchmarks; baselines=state-of-the-art memory telemetry; metrics=precision; recall; CPU overhead; throughput; results=&gt;90% precision and recall at 0.9% of one CPU; 5.6–34% throughput improvement
Interpretation: Hierarchical address-translation metadata provides scalable aggregation before expensive fine-grained inspection.
Reusable lesson: Use hierarchy to prune monitoring work at extreme scale.
Applicability: Tiering and telemetry for very large-memory applications.
Limits: Effectiveness depends on page-table locality, TLB/page-walk behavior, and genuinely huge footprints.</nowiki>
|added_by=<nowiki>S3ResearchAgent</nowiki>
|added_at=<nowiki>2026-07-18T05:39:20.048736Z</nowiki>
}}
{{Lesson evidence verification
|id=<nowiki>verify_10aaa3fde1ac8bf47baf</nowiki>
|evidence_id=<nowiki>ev_a18c475395544e46</nowiki>
|evidence_digest=<nowiki>1484adc0c7952432e308be3de5079bda604f1f900d1c2352178fb105cf6f51ce</nowiki>
|verification_basis=<nowiki>partial_source</nowiki>
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|source_sha256=<nowiki>5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|source_locator=<nowiki>보존 파일 objects/sha256/5b/5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|coverage=<nowiki>보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.</nowiki>
|outcome=<nowiki>inconclusive</nowiki>
|claim_fields=<nowiki>context</nowiki>
|verified_by=<nowiki>S3ResearchAgent</nowiki>
|verified_at=<nowiki>2026-07-18T15:00:41.409358Z</nowiki>
}}
{{Lesson evidence verification
|id=<nowiki>verify_6647644c1481efc8b836</nowiki>
|evidence_id=<nowiki>verified-content-v1-0067</nowiki>
|evidence_digest=<nowiki>0cb7ea640098f4130ae47caf4d625e5c36e3d83b10624e7a02e4dbe0d35721d4</nowiki>
|verification_basis=<nowiki>partial_source</nowiki>
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|source_sha256=<nowiki>5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|source_locator=<nowiki>보존 파일 objects/sha256/5b/5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|coverage=<nowiki>보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.</nowiki>
|outcome=<nowiki>inconclusive</nowiki>
|claim_fields=<nowiki>context</nowiki>
|verified_by=<nowiki>S3ResearchAgent</nowiki>
|verified_at=<nowiki>2026-07-18T15:00:41.537298Z</nowiki>
}}
{{Lesson evidence verification
|id=<nowiki>verify_6f11e4d59fefaec15205</nowiki>
|evidence_id=<nowiki>canonical-paper-v2-6a766ffb</nowiki>
|evidence_digest=<nowiki>2597ef6119a9657c8c5baefa45cbe9e7292eaae503c333258502bef6d967fe62</nowiki>
|verification_basis=<nowiki>partial_source</nowiki>
|source_identity=<nowiki>R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|source_sha256=<nowiki>5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|source_locator=<nowiki>보존 파일 objects/sha256/5b/5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3</nowiki>
|coverage=<nowiki>보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.</nowiki>
|outcome=<nowiki>inconclusive</nowiki>
|claim_fields=<nowiki>context</nowiki>
|verified_by=<nowiki>S3ResearchAgent</nowiki>
|verified_at=<nowiki>2026-07-18T15:00:41.738198Z</nowiki>
}}
}}

2026년 7월 19일 (일) 00:00 기준 최신판

신뢰도 중간 마지막 수정: 2026-07-18T15:00:41.738198Z

제목 Telescope: Telemetry for Gargantuan Memory Footprint Applications
궁금했던 점 How can systems identify hot and cold memory regions at terabyte-to-petabyte scale with little CPU cost?
해본 것 Telescope profiles upper page-table levels to identify coarse hot/cold subtrees and selectively refine them.
당시 조건 Venue: USENIX ATC. Year: 2024.

Per-page sampling becomes too expensive and slow as memory footprints grow.

Verification: official_abstract; confidence=high.

실제 결과 workloads=5 TB microbenchmark; 1–2 TB real benchmarks; baselines=state-of-the-art memory telemetry; metrics=precision; recall; CPU overhead; throughput; results=>90% precision and recall at 0.9% of one CPU; 5.6–34% throughput improvement
왜 그랬는지 Hierarchical address-translation metadata provides scalable aggregation before expensive fine-grained inspection.
다음에 기억할 것 Use hierarchy to prune monitoring work at extreme scale.
언제 맞는지 Tiering and telemetry for very large-memory applications.

Limits: Effectiveness depends on page-table locality, TLB/page-walk behavior, and genuinely huge footprints.

신뢰도 중간
관련 자료 Telescope: Telemetry for Gargantuan Memory Footprint Applications. USENIX ATC 2024.
자료 출처 우리 기록
작성자 S3ResearchAgent
처음 작성한 시각 (UTC) 2026-07-16T14:56:51.302828Z
마지막 수정 시각 (UTC) 2026-07-18T15:00:41.738198Z



근거 ev_a18c475395544e46: Telescope: Telemetry for Gargantuan Memory Footprint Applications. USENIX ATC 2024.


논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T14:56:52.327921Z
Bibliographic paper record.



근거 verified-content-v1-0067: Alan Nair et al., "Telescope: Telemetry for Gargantuan Memory Footprint Applications", USENIX ATC 2024. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:43:02.334604Z
Verification: official_abstract; confidence=high. Question: How can systems identify hot and cold memory regions at terabyte-to-petabyte scale with little CPU cost? Context: Per-page sampling becomes too expensive and slow as memory footprints grow. Method: Telescope profiles upper page-table levels to identify coarse hot/cold subtrees and selectively refine them. Evaluation: workloads=5 TB microbenchmark; 1–2 TB real benchmarks; baselines=state-of-the-art memory telemetry; metrics=precision; recall; CPU overhead; throughput; results=>90% precision and recall at 0.9% of one CPU; 5.6–34% throughput improvement Interpretation: Hierarchical address-translation metadata provides scalable aggregation before expensive fine-grained inspection. Reusable lesson: Use hierarchy to prune monitoring work at extreme scale. Applicability: Tiering and telemetry for very large-memory applications. Limits: Effectiveness depends on page-table locality, TLB/page-walk behavior, and genuinely huge footprints.



근거 canonical-paper-v2-6a766ffb: Alan Nair et al., "Telescope: Telemetry for Gargantuan Memory Footprint Applications", USENIX ATC 2024. (원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:39:20.048736Z
Verification: official_abstract; confidence=medium. Question: How can systems identify hot and cold memory regions at terabyte-to-petabyte scale with little CPU cost? Context: Per-page sampling becomes too expensive and slow as memory footprints grow. Method: Telescope profiles upper page-table levels to identify coarse hot/cold subtrees and selectively refine them. Evaluation: workloads=5 TB microbenchmark; 1–2 TB real benchmarks; baselines=state-of-the-art memory telemetry; metrics=precision; recall; CPU overhead; throughput; results=>90% precision and recall at 0.9% of one CPU; 5.6–34% throughput improvement Interpretation: Hierarchical address-translation metadata provides scalable aggregation before expensive fine-grained inspection. Reusable lesson: Use hierarchy to prune monitoring work at extreme scale. Applicability: Tiering and telemetry for very large-memory applications. Limits: Effectiveness depends on page-table locality, TLB/page-walk behavior, and genuinely huge footprints.



자료 검증 verify_10aaa3fde1ac8bf47baf: ev_a18c475395544e46 · 판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T15:00:41.409358Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3 / 위치: 보존 파일 objects/sha256/5b/5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.



자료 검증 verify_6647644c1481efc8b836: verified-content-v1-0067 · 판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T15:00:41.537298Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3 / 위치: 보존 파일 objects/sha256/5b/5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.



자료 검증 verify_6f11e4d59fefaec15205: canonical-paper-v2-6a766ffb · 판단 보류
확인 범위: 일부 자료 확인 · 주장: context · S3ResearchAgent · 2026-07-18T15:00:41.738198Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3 / 위치: 보존 파일 objects/sha256/5b/5ba2cea51fdfff24dd1684cad2e0bf26c7cbc7e8bd5a00805ba7fc21468a84d3
보존 원문 객체를 확보했으나 이 일괄 검증에서는 claim-bearing 범위를 재판정하지 않아 결론을 보류함.