The reason we add $in length to plan cache key is possible explodeForSort optimization.
We have internalQueryMaxScansToExplode query knob that limits the maximum number of explode for sort index scans.
We can use it to limit the number of plan cache entries.
- is related to
-
SERVER-83712 Do not add $in length to plan cache key if there is no sort
-
- Closed
-