[SERVER-68248] Implement one-pass for sorted and non-overlapping case in WT_MODIFY Created: 25/Jul/22 Updated: 28/Jul/22 Resolved: 28/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2022-07-25, Execution Team 2022-08-08 |
| Participants: |
| Description |
|
As discovered during analysis of WT_MODIFY. The case of time-series inserts is a sorted and non-overlapping case. WiredTiger however doesn't seem to think so and falls back to a series of intermediate materialisations of the changes. This ticket is about implementing a one-pass of the WT_MODIFY sequence in order to do a single materialisation instead of multiple. |