Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13278

Investigate changes in SERVER-44296: Report sufficient significant figures of Flow Control locksPerOp in FTDC

    XMLWordPrintable

    Details

      Description

      Description

      Downstream Change Summary

      The serverStats flowControl.locksPerOp field has been replaced by flowControl.locksPerKiloOp (to ensure sufficient significant figures are reported in FTDC).

      Description of Linked Ticket

      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

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 35 weeks, 3 days ago
                Date of 1st Reply: