[SERVER-13341] Cache single solution query plans Created: 25/Mar/14  Updated: 29/Jan/24

Status: Needs Scheduling
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-58317 $planCacheStats can incorrectly filte... Closed
is duplicated by SERVER-85595 [Classic] Cache single solution plans Closed
Related
related to SERVER-64315 Re-enable caching of single solution ... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

SERVER-75506 cached single solution plans in the classic engine when inside a $lookup, and saw up to a 9% improvement in TPCH benchmarks with no confirmed regressions. We should consider caching all single solution plans to get this perf improvement.

Originally we did not cache single solution plans in classic to save space in the cache, and because planning was "fast enough". However the cache may be faster in most cases so we should look into this.

SBE plans are always cached, and from what I've seen through $planCacheStats, they tend to take more space as well (compared to classic SolutionCacheData). So in terms of space it seems okay to cache classic plans always (of course this should be tested, and I also understand that the capacity limits are different for classic and SBE caches).


Generated at Thu Feb 08 03:31:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.