Write Performance History Store - Retain History Pages More Often

XMLWordPrintableJSON

    • Storage Engines, Storage Engines - Persistence
    • SE Persistence - 2026-01-30
    • None

      There is evidence during the YCSB 100 Update workload that history store content is being evicted from the cache, and subsequently re-read. That re-reading is happening in the critical path of checkpoint, which slows checkpoint creation down enough that it disrupts throughput.

      This particular workload has minimal cache pressure. We should understand why clean history store pages are being evicted when there is little cache pressure and they are subsequently required.

        1. image-2026-01-20-17-04-30-064.png
          779 kB
          Luke Pearson
        2. Screenshot 2026-01-13 at 2.02.59 pm.png
          151 kB
          Alexander Gorrod
        3. Screenshot 2026-01-13 at 2.05.36 pm.png
          105 kB
          Alexander Gorrod
        4. Screenshot 2026-01-13 at 2.20.24 pm.png
          104 kB
          Alexander Gorrod
        5. Screenshot 2026-01-14 at 3.41.12 pm.png
          164 kB
          Alexander Gorrod
        6. Screenshot 2026-01-14 at 7.25.20 am.png
          74 kB
          Alexander Gorrod
        7. Screenshot 2026-01-14 at 7.30.44 am.png
          67 kB
          Alexander Gorrod
        8. Screenshot 2026-01-19 at 10.01.50 pm.png
          86 kB
          Alexander Gorrod
        9. Screenshot 2026-01-19 at 10.03.21 pm.png
          100 kB
          Alexander Gorrod
        10. Screenshot 2026-01-19 at 9.58.44 pm.png
          89 kB
          Alexander Gorrod
        11. wt_16443_all_incl_ckpt_read_stats.diff
          118 kB
          Alexander Gorrod

            Assignee:
            Luke Pearson
            Reporter:
            Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: