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

Use WiredTiger cursor caching

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.10, 3.7.4
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • v3.6
    • Storage 2018-02-26, Storage Non-NYC 2018-04-09, Storage Non-NYC 2018-04-23
    • 0

      As part of WT-1228, we can enable cursor caching for WiredTiger in the integration layer. Originally, we intended to remove the cursor caching done in the integration layer. To get roughly equivalent performance, we should keep the caching at the integration layer (with a much lower count of cursors), and when a session is released, all cursors in the session will be closed. Closing the cursors will cache them in WiredTiger, so that reopens will be quick. Thus, this is called a hybrid scheme. It has the benefit of the original plan that we should be able to immediately drop or verify collections that are no longer in use.

            donald.anderson@mongodb.com Donald Anderson
            donald.anderson@mongodb.com Donald Anderson
            1 Vote for this issue
            12 Start watching this issue