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

overflow record tracking cleanup

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

      @michaelcahill, agorrod

      I'm going to take a run at speeding up our handling over overflow items, based on WT-330.

      As you know, the problem is if we're tracking overflow objects in reconciliation, we do linear walks/searches of potentially (really!) big lists of overflow items.

      The first step was to separate out the list of addresses we're tracking for discard from the list of overflow objects (the list of addresses is never searched or processed, it's a list of 1 or 2 addresses that get discarded when the page is successfully reconciled). That's the list that's making us allocate the tracking memory most of the time, and we only need on the order of 20B since a typical address is 7-8 bytes when using a POSIX file system.

      I've committed that change and the next step will be to replace the current overflow tracking software with some kind of skiplist based on the overflow item's hash.

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

              Created:
              Updated:
              Resolved: