[SERVER-3546] profiler: track time in disk io Created: 08/Aug/11  Updated: 06/Dec/22  Resolved: 06/Oct/17

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

Type: New Feature Priority: Major - P3
Reporter: Kenny Gorman Assignee: Backlog - Storage Execution Team
Resolution: Incomplete Votes: 6
Labels: rn
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-1815 instrument more detailed response tim... Closed
is related to SERVER-4678 More Metrics Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Track time doing actual disk io



 Comments   
Comment by Eric Milkie [ 06/Oct/17 ]

As specified, this ticket cannot be implemented, as it's not possible to ascribe individual disk I/O operations to a particular read or write statement.

Comment by Eliot Horowitz (Inactive) [ 12/Jun/12 ]

There is a lot more stuff tracked after SERVER-4628.
See list there.

Comment by Eliot Horowitz (Inactive) [ 31/May/12 ]

SERVER-4328 will cover a lot of this

Comment by Eliot Horowitz (Inactive) [ 01/Feb/12 ]

Not sure how accurate i/o time can be.
Can at least do something

Comment by Kenny Gorman [ 31/Jan/12 ]

The most useful stats would be:

I/O time. How long did this statement take for I/O time. The 'fetch' portion of the query for instance.
Lock time. How long did this statement wait due to waiting for locks.

Maybe the output was like:

{ "ts" : ISODate("2012-01-31T23:54:25.029Z"), 
  "op" : "query", 
  "ns" : "test.test", 
  "query" : { }, "nscanned" : 1, 
  "nreturned" : 1, "responseLength" : 55, 
  "responseTime":{"Totalmillis":22,"IOmillis":20,"Lockmillis":2}, 
  "client" : "127.0.0.1", 
  "user" : "" 
}

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