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

Increase planning time QO visibility metrics

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization

      Sometimes, like in HELP-69798, we suspect that the issues have little or nothing to do with planning time but we cannot really confidently tell since we have not enough visibility metrics into the planner. Therefore we should add FTDC metrics for:

      1. Query parsing time
      2. Qiery optimization time, defined as time spent into any heuristic optimizations we make to a CanonicalQuery (e.g: match expression optimization)
      3. Plan enumeration time
      4. Query planning time (time spent multi-planning)
      5. Time spent in SBE stagebuilders (if query was SBE eligible)
      6. Number of keys not found vs found but inactive vs found and active in plan cache
      7. Time waiting for the partitioned cache lock
      8. Time spent retrieving a plan from cache

            Assignee:
            peter.volk@mongodb.com Peter Volk
            Reporter:
            c.alonso@mongodb.com Carlos Alonso Pérez
            Votes:
            2 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: