We encode exact limit and skip values as part of cache key in SBE:
encodeSBE calls encodeFindCommandRequest] that encodes skip and limit values.
While encodeClassic doesn't do it.
This may cause plan cache bloat and excessive multi planning in SBE.
- related to
-
SERVER-84278 Don't generate plan cache entries for EOF plans
-
- Closed
-
-
-
- Closed
-
-
SERVER-83959 When preparing SBE plan, correctly pass preparingFromCache argument
-
- Closed
-