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

Check if a cached cursor exists before constructing configuration string in WiredTigerCursor

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
    • Fully Compatible
    • Execution Team 2020-06-29
    • 0

      When creating WiredTigerCursors, we construct the entire configuration string and pass that to WiredTigerSessionCache::getCachedCursor. The majority of normal cursors utilize the session cache, and the implementation of getCachedCursor doesn't use the configuration string if a cached cursor is found.

      Since cursor creation is in a hot path, we should first check the cache if a cursor is found, and only construct the configuration string for a new cursor when one isn't already open.

            Assignee:
            yuhong.zhang@mongodb.com Yuhong Zhang
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: