[SERVER-12796] Consider not caching plans if all candidates are equally unproductive Created: 19/Feb/14 Updated: 11/Jul/16 Resolved: 25/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | 2.6.0-rc1 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
If none of the candidate plans produce or hit EOF while picking the best plan, then we currently choose a plan arbitrarily and cache it. We should consider not caching the plan in this case, since we don't have much information suggesting that it is better than the other candidates. |
| Comments |
| Comment by Githook User [ 25/Feb/14 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: If the winning plan returns zero results but does not hit EOF, then we no longer cache it. Fixes a bug which would allow plans that did not hit EOF in the multi plan runner to be chosen over EOF plans. |