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

Reconsider spinlocks in transaction ID allocation path

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines
    • StorEng - Refinement Pipeline

      Summary
      We should re-evaluate the spinlocks added by WT-4571 in _txn_get_snapshot_int. This change results in some worse scaling at high thread levels in some workloads with many readers and writers.

      Motivation
      Our investigation in SERVER-55030 led us to conclude that the main source of contention in workloads with many readers and writers is the spinlock inside _txn_get_snapshot_int. By adding a short sleep in this loop, we were able to demonstrate improved performance for some workloads.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            41 Vote for this issue
            Watchers:
            33 Start watching this issue

              Created:
              Updated: