Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4105

Optimize cache usage for update workload with history pinned

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.6, 4.0.0-rc5, WT3.1.0, 4.1.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Non-NYC 2018-06-04, Storage Non-NYC 2018-06-18

      Workloads that insert a large value, and then do many WT_CURSOR->modify operations to make many small updates to the value while holding the oldest transaction/timestamp pinned can generate very large pages in cache, and force us to regularly re-write the page via lookaside.

      Which leads to effectively pinning the cache full.

      We could do better by decreasing how often we instantiate a full value in such workloads, so there is less memory pinned in cache.

            vamsi.krishna@mongodb.com Vamsi Boyapati
            alexander.gorrod@mongodb.com Alexander Gorrod
            0 Vote for this issue
            7 Start watching this issue