Don't keep transaction IDs pinned for reading from checkpoints

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • WT2.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None

      We currently treat all btree cursors the same, and make sure that a transactional context is setup for reads before the cursor is positioned. However, for cursors on checkpoints, this is unnecessary because checkpoints are read-only and thus don't need to distinguish between multiple versions of updates.

      There are several workloads that should be improved by not allocating snapshots when reading from checkpoints, including test/checkpoint and LSM Bloom / merge operations.

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

                Created:
                Updated:
                Resolved: