-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
(copied to CRM)
-
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:
- Query parsing time
- Query optimization time, defined as time spent into any heuristic optimizations we make to a CanonicalQuery (e.g: match expression optimization)
- Plan enumeration time
- 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.
- is derived by
-
SERVER-103360 Increase visibility into time spent within the query cache
-
- Backlog
-
-
SERVER-103371 Increase visibility into time spent during the SBE stagebuilders
-
- Backlog
-
- related to
-
SERVER-92476 planningTimeMicros can include work not related to planning
-
- Closed
-