Lookaside optimization: birthmarks

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.3, 3.7.1, WT3.1.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2017-12-04, Storage 2017-12-18
    • None
    • v3.6

      If we had "birthmarks", an inverse of tombstones (WT_UPDATE with type WT_UPDATE_DELETED), with the following sematics:

      • if a birthmark is not visible, it is equivalent to a tombstone; and
      • if a birthmark is visible, the on-page value is returned.

      Then when saving updates for lookaside eviction or update / restore, we could create a birthmark in the saved update list instead of making a full copy of the on-page value. For many common cases, this could dramatically reduce the amount of data that has to be written to the lookaside table (or stored in cache).

              Assignee:
              Keith Bostic (Inactive)
              Reporter:
              Michael Cahill (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: