[SERVER-72440] Deprioritize collection scans under load Created: 29/Dec/22 Updated: 29/Oct/23 Resolved: 28/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Execution Team 2023-03-06, Execution Team 2023-03-20, Execution Team 2023-04-03 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 131 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Under load, user collection scans should be given the lowest scheduling priority over all queries |
| Comments |
| Comment by Githook User [ 28/Mar/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |
| Comment by Gregory Noma [ 03/Mar/23 ] |
|
I split out index scans to |
| Comment by Haley Connelly [ 01/Mar/23 ] |
|
Agreed. I think unbounded here is key. |
| Comment by Daniel Gomez Ferro [ 06/Feb/23 ] |
|
I think this should deprioritize all unbounded scans on collections (both clustered and non-clustered) and indexes. |
| Comment by Haley Connelly [ 06/Feb/23 ] |
|
This ticket should make sure that collection scans on clustered indexes are not penalised the same as non-clustered collection scans. |