[SERVER-34454] Consider including the EOF bonus in the plan cache score Created: 13/Apr/18 Updated: 29/Oct/23 Resolved: 09/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chris Harris | Assignee: | Timour Katchaounov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Query 2021-01-25, Query Optimization 2021-02-22 | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
Currently, EOF bonuses are stripped from plan scores prior to being saved in the plan cache. This comment implies that the logic relates to plan eviction. This seems to no longer apply due to the replanning mechanism that was introduced in 3.0. This may result in getPlansByQuery() output where the first plan listed (the winning/cached plan) has a lower score than subsequent entries. |
| Comments |
| Comment by Githook User [ 09/Feb/21 ] |
|
Author: {'name': 'Timour Katchaounov', 'email': 'timour.katchaounov@mongodb.com'}Message: Removes the subtraction of the eofBonus from the final score, This is safe to do because the cached score is used only for logging |