[SERVER-44296] Report sufficient significant figures of Flow Control locksPerOp in FTDC Created: 29/Oct/19 Updated: 29/Oct/23 Resolved: 10/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Daniel Ernst |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | groomed, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Sprint: | Execution Team 2019-12-16 | ||||||||
| Participants: | |||||||||
| Description |
|
Numerical data in FTDC is stored as 64-bit integers. Flow Control locksPerOp is a floating point value, and is rounded down to 0 in FTDC when its value is < 1. Some ways to ensure this are:
|
| Comments |
| Comment by Githook User [ 10/Dec/19 ] |
|
Author: {'email': 'daniel.ernst@mongodb.com', 'name': 'Daniel Ernst'}Message: This prevents locksPerOp from being rounded down to 0 in FTDC |