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

Optimize cache usage for update workload with history pinned

    XMLWordPrintable

    Details

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

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vamsi.krishna Vamsi Boyapati
              Reporter:
              alexander.gorrod Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: