[SERVER-82473] Use timestamp_transaction_uint in setStableTimestamp and setOldestTimestamp Created: 26/Oct/23 Updated: 13/Nov/23 Resolved: 13/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Mark Benvenuto |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Security 2023-11-13, Security 2023-11-27 |
| Participants: |
| Description |
|
When force=false, we should use WT's timestamp_transaction_uint which avoids all the overhead of generating a string and parsing it. I have not measured the overall perf impact of this change but I believe it will be neglible. |
| Comments |
| Comment by Mark Benvenuto [ 13/Nov/23 ] |
|
WT does not have this api on the connection level, only on the session level unforunately. |