Lesson:avoiding read stalls on flash storage 34c6809a
| 제목 | Avoiding Read Stalls on Flash Storage |
|---|---|
| 궁금했던 점 | Can a buffer manager serve cache-miss reads immediately when every frame is dirty? |
| 해본 것 | WAR copies the dirty LRU-tail page to a DRAM staging area, immediately reuses the frame for the read, and flushes the copy asynchronously. |
| 당시 조건 | Venue: SIGMOD. Year: 2022.
Read-after-writeback (RAW) stalls the foreground read until a dirty victim page is flushed to flash. Verification: official_abstract; confidence=high. |
| 실제 결과 | workloads=MySQL/InnoDB; Zero; baselines=RAW read-after-writeback; metrics=transaction throughput; read latency; stall time; results=up to 2.9x transaction throughput |
| 왜 그랬는지 | A cheap memory copy can remove a long storage dependency from the foreground path. |
| 다음에 기억할 것 | Use bounded staging to decouple latency-critical allocation from slow durable writeback. |
| 언제 맞는지 | Flash-backed databases and buffer caches under dirty-page pressure.
Limits: Requires extra DRAM and careful ordering/recovery; value falls when dirty-victim stalls are rare. |
| 신뢰도 | 중간 |
| 관련 자료 | Avoiding Read Stalls on Flash Storage. SIGMOD 2022. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T14:57:02.598514Z |
| 마지막 수정 시각 (UTC) | 2026-07-18T14:58:19.579137Z |
근거 ev_c7e5709749514d1a: Avoiding Read Stalls on Flash Storage. SIGMOD 2022.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T14:57:04.586368Z
Bibliographic paper record.
근거 verified-content-v1-0072: Mijin An et al., "Avoiding Read Stalls on Flash Storage", SIGMOD 2022.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:43:21.943175Z
Verification: official_abstract; confidence=high.
Question: Can a buffer manager serve cache-miss reads immediately when every frame is dirty?
Context: Read-after-writeback (RAW) stalls the foreground read until a dirty victim page is flushed to flash.
Method: WAR copies the dirty LRU-tail page to a DRAM staging area, immediately reuses the frame for the read, and flushes the copy asynchronously.
Evaluation: workloads=MySQL/InnoDB; Zero; baselines=RAW read-after-writeback; metrics=transaction throughput; read latency; stall time; results=up to 2.9x transaction throughput
Interpretation: A cheap memory copy can remove a long storage dependency from the foreground path.
Reusable lesson: Use bounded staging to decouple latency-critical allocation from slow durable writeback.
Applicability: Flash-backed databases and buffer caches under dirty-page pressure.
Limits: Requires extra DRAM and careful ordering/recovery; value falls when dirty-victim stalls are rare.
근거 canonical-paper-v2-34c6809a: Mijin An et al., "Avoiding Read Stalls on Flash Storage", SIGMOD 2022.
(원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:13:48.998350Z
Verification: official_abstract; confidence=medium.
Question: Can a buffer manager serve cache-miss reads immediately when every frame is dirty?
Context: Read-after-writeback (RAW) stalls the foreground read until a dirty victim page is flushed to flash.
Method: WAR copies the dirty LRU-tail page to a DRAM staging area, immediately reuses the frame for the read, and flushes the copy asynchronously.
Evaluation: workloads=MySQL/InnoDB; Zero; baselines=RAW read-after-writeback; metrics=transaction throughput; read latency; stall time; results=up to 2.9x transaction throughput
Interpretation: A cheap memory copy can remove a long storage dependency from the foreground path.
Reusable lesson: Use bounded staging to decouple latency-critical allocation from slow durable writeback.
Applicability: Flash-backed databases and buffer caches under dirty-page pressure.
Limits: Requires extra DRAM and careful ordering/recovery; value falls when dirty-victim stalls are rare.
자료 검증 verify_b04ce9dbd14cf1584e8c:
ev_c7e5709749514d1a ·
판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:19.579137Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 / 위치: 보존 파일 manifest.json
수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함.