[SERVER-67101] Support microsecond precision in ScopedTimer Created: 08/Jun/22 Updated: 29/Oct/23 Resolved: 28/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ruoxin Xu | Assignee: | Ruoxin Xu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | M2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QO 2022-06-13, QO 2022-06-27, QO 2022-07-11, QO 2022-07-25, QO 2022-08-08 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 1 | ||||||||
| Description |
|
We should collect more precise estimates of execution time. The ScopedTimer currently uses a SystemClockSource which only has millisecond precision generating imprecise and unstable estimates in some cases. Consider replacing the SystemClockSource with the SystemTickSource. Expected outcome of this ticket:
|
| Comments |
| Comment by Githook User [ 27/Jul/22 ] |
|
Author: {'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}Message: |
| Comment by Githook User [ 26/Jul/22 ] |
|
Author: {'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}Message: Revert " This reverts commit e7d2be0dae29265e2a6efafd4753debf11b9e96f. |
| Comment by Githook User [ 26/Jul/22 ] |
|
Author: {'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}Message: |