Investigate $queryStats performance with no rate limit

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • 5
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As seen in BF-30845, there is a change in $queryStats performance related to SERVER-79736. This is only for the case when $queryStats is invoked concurrently with find commands with no rate limit. We spent some time looking into this and ruled out some theories, but ultimately did not get to the bottom of it. If the rate limit is ever turned off and/or if we would want to run $queryStats more often, it would be good to know the root cause for the regression.

              Assignee:
              [DO NOT USE] Backlog - Query Integration
              Reporter:
              Erin Zhu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: