Issue Summary

There are currently multiple methods for retrieving the time in the codebase, specifically _wt_epoch and rdtsc. This redundancy may be unnecessary and could impact performance. The team discussed the need to review all uses of _wt_epoch and consider replacing them with rdtsc where appropriate.

Context

• The discussion was prompted by WT-17889, which may lead to performance improvements.
• Having two different ways to get the time is not ideal for maintainability or performance.
• The proposal is to audit all __wt_epoch calls and assess if they should be replaced with rdtsc.
• Findings can be split per sub-team after the initial review.

Proposed Solution

• Audit all uses of __wt_epoch in the codebase.
• Assess whether each instance can be replaced with rdtsc for consistency and potential performance gains.
• After the initial audit, split the findings among relevant sub-teams for implementation.

Original Slack thread: Slack Thread
This ticket was generated by AI from a Slack thread.