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

Improve concurrency in the transaction subsystem

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.11, WT3.0.0
    • Component/s: None
    • Labels:
      None

      Description

      There is currently a single rwlock protecting reads and writes of data in WT_TXN_GLOBAL. Some of those operations, such as updating the oldest transaction (and timestamp), involve scans that are O(#open sessions).

      Performance should be better with more granular locking, where transactions put themselves on a number of lists (one by transaction ID, one by pinned ID, one by read timestamp, and another by commit timestamp). Each of those lists can be protected by a rwlock, and transactions would only appear in a list when they have the associated ID / timestamp.

      This should make update_oldest into an O(1) operation, and make get_snapshot O(#running transactions) rather than O(#open sessions).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                michael.cahill Michael Cahill
                Reporter:
                michael.cahill Michael Cahill
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: