[SERVER-63701] Log implementation of SystemTickSource at startup Created: 15/Feb/22 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
On posix systems, there are 2 possible implementations of SystemTickSource. Systems that report the availability of a posix monotonic clock use it, otherwise they use the system wall clock. We should log at startup which clock source is in use, and perhaps also write a unit test to ensure that the monotonic source is used on systems that support it. |
| Comments |
| Comment by Andy Schwerin [ 18/Mar/22 ] |
|
I think it would be most useful in debugging build failures in the CI system. |
| Comment by Blake Oler [ 16/Mar/22 ] |
|
Ping schwerin |
| Comment by Blake Oler [ 24/Feb/22 ] |
|
Or, in what scenarios would they benefit from the results of this ticket? |
| Comment by Blake Oler [ 24/Feb/22 ] |
|
Yes, but how do you envision somebody making use of the results of this ticket? |
| Comment by Andy Schwerin [ 24/Feb/22 ] |
|
The two tick sources have different properties, potentially. |