[SERVER-83287] Ixscan plans on unique indexes needlessly call next() on storage cursor Created: 15/Nov/23 Updated: 25/Jan/24 Resolved: 17/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Zixuan Zhuang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | auto-reverted, query-perf-q4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 154 | ||||||||||||||||
| Description |
|
When we make an index scan SBE plan with point bounds, we end up calling next() in the storage layer more than once, even though a unique index guarantees that there can only be one key. We should consider optimizing this. |
| Comments |
| Comment by Githook User [ 25/Jan/24 ] |
|
Author: {'name': 'Zixuan', 'email': 'leozzx@users.noreply.github.com', 'username': 'leozzx'}Message: GitOrigin-RevId: eacfd09bc2bca2abc0206dba154c23029fe08558 |
| Comment by Githook User [ 17/Jan/24 ] |
|
Author: {'name': 'Zixuan', 'email': 'leozzx@users.noreply.github.com', 'username': 'leozzx'}Message: GitOrigin-RevId: 7fdf7fe84fb9b8cc8504b63b2a4ae0836c9d320f |
| Comment by Githook User [ 11/Jan/24 ] |
|
Author: {'name': 'auto-revert-processor', 'email': 'dev-prod-dag@mongodb.com', 'username': ''}Message: Revert " This reverts commit 88cd25c553792dd4cbd07c139a616eff7fcdf90c. GitOrigin-RevId: 2bcfeb7bb5ced13bee74d6a064b2c2dafb540809 |
| Comment by Githook User [ 10/Jan/24 ] |
|
Author: {'name': 'Zixuan', 'email': 'leozzx@users.noreply.github.com', 'username': 'leozzx'}Message: GitOrigin-RevId: 88cd25c553792dd4cbd07c139a616eff7fcdf90c |