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
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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. Query 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)

      – Do note that this is a series of tickets to increase visibility. These tickets are sliced to be able to be delivered in a timely manner.

            Assignee:
            Unassigned Unassigned
            Reporter:
            c.alonso@mongodb.com Carlos Alonso Pérez
            Votes:
            2 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: