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

timestamp abort does not need to increment with atomic op

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 3.6.0-rc0, WT3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2017-10-02

      In WT-3512 the use of timestamps in timestamp_abort changed to use a rwlock so that the oldest/stable timestamps did not get used in an incorrect way. That change also changed a simple increment into an atomic increment.

      The atomic operation results in 13% fewer operations being completed during the test. If an increment gets lost because it is not atomic and/or two threads use the same value, that is okay and does not affect test correctness. It is beneficial to have more operations in play for this abort test.

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: