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

Improve cache tracking for small uncompressed pages

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 5
    • 2023-05-16 Chook-n-Nuts Farm, 2023-05-02 StorEng Bug Bash, 2023-05-30 - 7.0 Readiness, StorEng - 2023-06-13, 2023-06-27 Lord of the Sprints, 2023-07-11 WiredTractor

      We recently encountered a case where a table had a lot of small on-disk pages (containing about 600bytes of data), with an allocation size of 4kb.

      That means that the on-disk space usage is inefficient, using 4kb for every 600 bytes of data. It also leads to the cache tracking in WiredTiger being inaccurate. Since the cache tracking is based on the data size, but block sized memory is allocated.

      This ticket should change how we manage and/or track the memory so that cache tracking is more accurate.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: