Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-13449

Review cursor caching

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines
    • StorEng - Defined Pipeline

      Review why/if we need the cursors to be cached.

      Why the "cursor open/close" operation can be slow? Can the slowness be eliminated, thus removing the need to cache cursors?

      What else is impacted by cursor opens/closes? Performance, data size, history store, checkpoints, eviction, etc.

      Connection with long running queries?

      Consider Server's "cursor yielding" technique.

        1. screenshot-1.png
          982 kB
          Yury Ershov

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            y.ershov@mongodb.com Yury Ershov
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: