Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35657

Do not delay journal flushes when operations are waiting for oplog visibility

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.9, 4.0.3, 4.1.3
    • Affects Version/s: 3.6.6, 4.0.0-rc5
    • Component/s: Storage
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Hide

      1. Configure 1-node replica set
      2. Select any benchmark with a mix of updates and reads (I chose YCSB)
      3. Compare performance between read concern majority, non-causal against read concern local, causal.

      Show
      1. Configure 1-node replica set 2. Select any benchmark with a mix of updates and reads (I chose YCSB) 3. Compare performance between read concern majority, non-causal against read concern local, causal.
    • Storage NYC 2018-07-02, Storage NYC 2018-07-16, Storage NYC 2018-07-30, Storage NYC 2018-08-13, Storage NYC 2018-08-27
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In a recent examination of transactions performance it was observed that specific combinations of read concern, topology, and causal settings caused significant performance slowdowns for read operations. Most notably the single-node replica sets using local read concern and causal consistency. In a build failure ticket we tracked this to the following work: SERVER-31679

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            cristopher.stauffer@mongodb.com Cristopher Stauffer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None