-
Type: Investigation
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Developer Tools
-
Not Needed
Original Downstream Change Summary
I'm not adding a new field here but populating it instead (was always 0). The field in particular is queryPlanner.optimizationTimeMillis
Description of Linked Ticket
Add a parameter to the explain output indicating the time spent evaluating the candidate plans in the multi-planner. There are some scenarios where the the multi-planner ends up taking a lot more time than the actual query execution. We should probably add this parameter conditionally if the time spend multi-planning exceeded certain threshold (maybe 100ms)
- depends on
-
SERVER-73498 Add time spent in the multi-planner to the explain output
- Closed