[SERVER-18922] Choose time source for measuring short durations dynamically at startup Created: 11/Jun/15 Updated: 19/Aug/20 Resolved: 19/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | PM-733, move-sa, platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
On different hardware and under different virtualization environments, the latency of reading the system clock can fluctuate by over 1000x. When the clock may be read with extremely low latency, we would like to leverage it to provide very precise timing information for operation latencies inside the server. When the system clock is of higher latency, we would like to emulate a low-resolution clock that can be read very quickly, so that timing calls on such systems do not interfere with the execution of actual user operations. |
| Comments |
| Comment by Benjamin Caimano (Inactive) [ 19/Aug/20 ] |
|
I've closed this ticket out since we landed a commit many versions ago. c46879f allows us to choose a tick source but only provides a single implementation. If you still feel we need the implementation described, please open a new ticket. |
| Comment by Githook User [ 12/Jun/15 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |