[SERVER-2778] Microsecond or nanosecond accuracy in query timing/currentop Created: 17/Mar/11  Updated: 13/May/15  Resolved: 13/May/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Remon van Vliet Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-13368 Need to expose better timing informat... Closed
Participants:

 Description   

It would be a lot more useful if query execution times are reported at a higher accuracy than milliseconds. Measuring in milliseconds in mongo is akin to measuring the 100m sprint in minutes for us . Whether it becomes ms but in floating point or micro/nanoseconds isn't important to me. If you run 40-50k ops per machine per second they're always going to be either 0 or 1 milliseconds (with some hickups here and there) which makes it hard to tweak the system.



 Comments   
Comment by Ramon Fernandez Marina [ 13/May/15 ]

Timing information in milliseconds for currentOps implemented in SERVER-13368.

Generated at Thu Feb 08 03:01:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.