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

Significant slowdown in capped collection performance when cap reached

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 2.8.0-rc5
    • None
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Hide

      Same workload and setup as SERVER-16697. Test runs well and quickly fills collection on a C3-4xl EC2 machine, the number of client threads (100) may need to be reduced on less capable hardware.

      mongod --storageEngine=wiredTiger --wiredTigerCacheSizeGB 1

      $ git clone https://github.com/wiredtiger/mongo-tests.git
      $ cd mongo-tests/SERVER-16697/
      $ mongo --quiet 16697.js 

      Show
      Same workload and setup as SERVER-16697 . Test runs well and quickly fills collection on a C3-4xl EC2 machine, the number of client threads (100) may need to be reduced on less capable hardware. mongod --storageEngine=wiredTiger --wiredTigerCacheSizeGB 1 $ git clone https://github.com/wiredtiger/mongo-tests.git $ cd mongo-tests/SERVER-16697/ $ mongo --quiet 16697.js

    Description

      When a smaller cache is used (1GB) and a high insert workload is applied to a capped collection, high insert latencies are seen once the collection reaches the capped value.

      Attachments

        Issue Links

          Activity

            People

              mathias@mongodb.com Mathias Stearn
              darren.wood@10gen.com Darren Wood
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: