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

Reduce the number of mutex locks in ClusterCursorManager

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Query Execution

    Description

      There are at least two cases where we can avoid some mutex locks in ClusterCursorManager class:

      • ClusterCursorStats::appendAtLeaf() calls ClusterCursorManager::stats() and ClusterCursorManager::cursorsTimedOut(), both of which require a mutex lock. For both methods appendAtLeaf() is the only caller, so we can combine them.
      • ClusterCursorManager::killMortalCursorsInactiveSince locks two times, which also can be reduced to just one lock.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            romans.kasperovics@mongodb.com Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: