]> 2026-09-08T17:12:41+09:00 Lesson:avoiding read stalls on flash storage 34c6809a 3000 ko 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. WAR copies the dirty LRU-tail page to a DRAM staging area, immediately reuses the frame for the read, and flushes the copy asynchronously. S3ResearchAgent medium 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. 2026-07-16T14:57:02Z 2461238.1229398 Avoiding Read Stalls on Flash Storage. SIGMOD 2022. A cheap memory copy can remove a long storage dependency from the foreground path. Avoiding Read Stalls on Flash Storage workloads=MySQL/InnoDB; Zero; baselines=RAW read-after-writeback; metrics=transaction throughput; read latency; stall time; results=up to 2.9x transaction throughput Can a buffer manager serve cache-miss reads immediately when every frame is dirty? lab Use bounded staging to decouple latency-critical allocation from slow durable writeback. Draft 2026-07-18T14:58:19Z 2461240.123831 2026-07-18T14:58:20Z 2461240.1238426 avoiding read stalls on flash storage 34c6809a 3000 ev_c7e5709749514d1a 2026-07-16T14:57:04Z 2461238.122963 S3ResearchAgent Avoiding Read Stalls on Flash Storage. SIGMOD 2022. paper Bibliographic paper record. not_recorded avoiding read stalls on flash storage 34c6809a# 00b9424fafb0d0e65645ee6c5663ffb3 3000 verified-content-v1-0072 2026-07-16T18:43:21Z 2461238.2801042 S3ResearchAgent Mijin An et al., "Avoiding Read Stalls on Flash Storage", SIGMOD 2022. paper 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. not_recorded avoiding read stalls on flash storage 34c6809a# eb6da28e4061929e6db9f2befbaa3f6b 3000 canonical-paper-v2-34c6809a 2026-07-18T05:13:48Z 2461239.7179167 S3ResearchAgent Mijin An et al., "Avoiding Read Stalls on Flash Storage", SIGMOD 2022. paper 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. official_abstract avoiding read stalls on flash storage 34c6809a# 880b83cbf4b8067ff1958cf391abce2f 3000 2026-07-18T14:58:19Z 2461240.123831 S3ResearchAgent verify_b04ce9dbd14cf1584e8c metadata_only context 수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함. inconclusive 689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 보존 파일 manifest.json ev_c7e5709749514d1a d5365490744f3a1f4d97adb3fbb2b42daa65858f193064c8ee44bb0c144b3641 avoiding read stalls on flash storage 34c6809a# 37cc60cf0d418748d83e7e090a9a88dc 3000 2026-07-18T14:58:19Z 2461240.123831 S3ResearchAgent verify_f4fc5583b53c23ecc045 metadata_only context 수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함. inconclusive 689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 보존 파일 manifest.json verified-content-v1-0072 1f8c69686a97c8df2b89d94a67e799c4079c02570e314883c4babc8e5d904311 avoiding read stalls on flash storage 34c6809a# c9b1b4a8b0bbc736d8814506b5cff464 3000 2026-07-18T14:58:19Z 2461240.123831 S3ResearchAgent verify_1c2c551a7d61218989f6 metadata_only context 수집 manifest의 실패 원장만 보존되어 원문 주장을 검증하지 못함. inconclusive 689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=689990da723c183d73e5102f6b5a7c8972497dfa210f09dd79bb20472fb857d5 보존 파일 manifest.json canonical-paper-v2-34c6809a 4d6ce7ec5605543723bfc931a78016efd90d1a84212d948039cbeae2cee86e4c avoiding read stalls on flash storage 34c6809a# de8a2d9553e1c8a9c25f6ef855ce4281