[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: |
|
||||||||||||||||
| 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 | |||||||||
| Comment by Eliot Horowitz (Inactive) [ 31/May/12 ] | |||||||||
|
| |||||||||
| Comment by Eliot Horowitz (Inactive) [ 01/Feb/12 ] | |||||||||
|
Not sure how accurate i/o time can be. | |||||||||
| 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. Maybe the output was like:
|