[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: |
|
||||||||
| 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 |
| Comments |
| Comment by Ramon Fernandez Marina [ 13/May/15 ] |
|
Timing information in milliseconds for currentOps implemented in |