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

Some workloads see more transaction conflicts with WT_CURSOR::modify

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • None
    • None
    • None
    • Storage 2017-11-13, Storage 2017-12-04

    Description

      We have noticed that since enabling the use of WT_CURSOR::modify via the MongoDB updateWithDamages interface, the number of write conflicts returned has increased significantly.

      A particular example is running a YCSB 50/50 read/update workload. The additional conflicts can lead to a reduced performance, since the operations need to be retried.

      We need to investigate why the number of conflicts increased, and hopefully reduce the occurrence.

      Attachments

        Issue Links

          is caused by

          Improvement - An improvement or enhancement to an existing feature or task. WT-3752 WiredTiger can walk long update chains for hot rows.

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. WT-3530 YCSB performance regressions in master vs. 3.4 and 3.5.

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. WT-3747 workgen: add support for WT_CURSOR::modify

          • Major - P3 - Major loss of function.
          • Backlog

          Activity

            People

              keith.bostic@mongodb.com Keith Bostic (Inactive)
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: