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

Reconciliation's handling of the page's memory footprint could be improved.

    • Type: Icon: Task Task
    • Resolution: Done
    • WT1.6.0
    • Affects Version/s: None
    • Component/s: None

      1. Tracked overflow items don't increment the page's memory footprint.
      2. Split-merge pages created by reconciliation aren't reflected in the current page's memory footprint. Because split-merge pages stay in memory in order to support future eviction of the page, they should be part of the page's memory footprint. Note, the memory footprint should increase/decrease each time the page is reconciled, as previously created split-merge pages are discarded on each new reconciliation.
      3. Split-merge pages created by reconciliation don't have their memory footprint set when they're created. As split-merge pages can't be evicted, this probably doesn't matter for eviction, but it does matter for overall cache size.

            Assignee:
            Unassigned Unassigned
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: