[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:
Documented
is documented by DOCS-13278 Investigate changes in SERVER-44296: ... Closed
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.
locksPerOp is expected to be less than 1 in certain batch write scenarios, so it is important to ensure that it still gets reported as nonzero in these scenarios.

Some ways to ensure this are:

  1. Report opsPerLock in addition to locksPerOp
  2. Multiply locksPerOp by some constant multiple of 10 to ensure sufficient significant figures


 Comments   
Comment by Githook User [ 10/Dec/19 ]

Author:

{'email': 'daniel.ernst@mongodb.com', 'name': 'Daniel Ernst'}

Message: SERVER-44296 Report locksPerKiloOp in Flow Control instead of locksPerOp

This prevents locksPerOp from being rounded down to 0 in FTDC
Branch: master
https://github.com/mongodb/mongo/commit/8c00a6ebe6d3f1fbca9b9e0b297e1b130a4e98f9

Generated at Thu Feb 08 05:05:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.