[SERVER-64830] Simplify exclusivity tracking in IndexSeekPoint Created: 23/Mar/22 Updated: 29/Oct/23 Resolved: 01/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2022-04-04 |
| Participants: |
| Description |
|
Currently we maintain a bool _prefixExclusive and a vector of bools _suffixInclusive. What we actually need to know is whether there is an exclusive field, and if so, what is the index of the first exclusive field. This can be tracked with a single int. It's a very small change, but it allows us to simplify our checks in IndexEntryComparison::makeKeyStringFromSeekPointForSeek and leads to a modest but non-trivial speed-up in seek-heavy workloads when the index fits in memory. |
| Comments |
| Comment by Githook User [ 01/Apr/22 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |