[SERVER-8310] Add current_clock_source and available_clock_source to db.hostInfo() Created: 24/Jan/13 Updated: 21/May/19 Resolved: 19/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | PM-733, polish | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux only |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
We've seen perf differences depending on which clock is used. |
| Comments |
| Comment by Mira Carey [ 19/Apr/19 ] |
|
This ticket isn't really relevant anymore. Our current system contains a precise and fast clock, which the precise clock as the system clock, and the fast clock as a "updated by a background thread, or by callers of the system clock" We do see perf differences based on which clock is used, but have larger migrated callers that need to check time very frequently to use the fast clock |