[SERVER-15124] Eviction algorithm for bad cached plans needs to be more aggressive Created: 03/Sep/14  Updated: 17/Feb/15  Resolved: 17/Feb/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 2.6.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Asya Kamsky Assignee: David Storch
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-15225 CachedPlanStage should execute for tr... Closed
Related
related to SERVER-15924 planCacheListPlans command can report... Closed
Operating System: ALL
Sprint: Query 2.7.8
Participants:

 Description   

When we cache a plan, if subsequent queries produce significantly worse performance result than expected, the cached plan should be evicted.

It's currently evicted but the eviction strategy is too conservative so if we happen to cache a plan that works well only on a small minority of values we take too long to replace it.



 Comments   
Comment by David Storch [ 17/Feb/15 ]

Work for this ticket is now being done under SERVER-15225. Closing as a duplicate.

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