[SERVER-72638] Loss of precision in duration measurement of insertion of keys from sorter into index Created: 09/Jan/23  Updated: 29/Oct/23  Resolved: 10/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: George Wangensteen Assignee: George Wangensteen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Service Arch 2023-01-23
Participants:

 Description   

We time the duration of time it takes to insert keys from the sorter into the index as part of the index building process, and log this duration at default level. See here However the way we covert the timed duration to Milliseconds to log loses precision and we end up losing any sub-second granularity. For short-running index builds this makes the log line less useful as we lose information about how long this step is taking. This is quick to fix by changing the conversion to Milliseconds to use duration cast, as the Timer itself has adequate granularity. 



 Comments   
Comment by Githook User [ 10/Jan/23 ]

Author:

{'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}

Message: SERVER-72638 Fix duration precision loss in bulk_builder_common log line
Branch: master
https://github.com/mongodb/mongo/commit/4397941a80101eefd7093604a87ce4fce111975e

Generated at Thu Feb 08 06:22:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.