The classic engine and SBE have completely different implementations of multi-planning (a.k.a. runtime plan selection). In SERVER-62981, we separated the internalQueryPlanEvaluationCollFraction knob into two. That is, we introduced a new internalQueryPlanEvaluationCollFractionSbe knob which applies only to SBE and changed internalQueryPlanEvaluationCollFraction so that it applies only the classic engine. Since the two multi-planning implementations are distinct and may have different properties, it should be possible for users to tune their behavior independently.
In the same vein, we should separate internalQueryPlanEvaluationWorks into two knobs. Again, internalQueryPlanEvaluationWorks would be just for the classic engine and internalQueryPlanEvaluationWorksSbe would apply only to SBE. That way, if the default value of 10,000 for SBE proves to be too low, users or support engineers can increase its value without disturbing the behavior of queries using the classic engine.
- is related to
-
SERVER-62150 SBE Multiplanning can be slow when suboptimal plan runs first
- Closed
-
SERVER-62981 Make SBE multi-planner's trial period termination condition independent of collection size
- Closed