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

Set wiredTigerConcurrentReadTransactions based on machine specs?

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • WiredTiger

    Description

      I see that there's a setting for wiredTigerConcurrentReadTransactions. We appear to be sometimes hitting this. I'm not really sure why this exists, but it appears to potentially be artificially capping throughput? If you have a really beefy machine, then you should be able to handle more concurrent read transactions? Is there any reason we shouldn't raise it? Does it increase contention to a point where things slow down more than they are sped up?

      I see a brief reference to being able to change it in the docs (http://docs.mongodb.org/manual/reference/parameters/), but it's not clear to me if I should or what the implications are.

      Attachments

        1. 1hour.png
          1hour.png
          71 kB
        2. 4hours.png
          4hours.png
          65 kB

        Activity

          People

            michael.cahill@mongodb.com Michael Cahill
            chengas123 Ben McCann
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: