sysdig icon indicating copy to clipboard operation
sysdig copied to clipboard

Tools for tracking down I/O Wait

Open eMPee584 opened this issue 2 years ago • 3 comments

Because in practice, systems often get stuck in high iowait scenarios, it would be great to have tools for diagnosing this in sysdig. Example questions would be:

  • Which application has stuck IO in flight?
  • Which files and which storage blocks are being accessed?
  • Stalling due to networked filesystems connection failure / starving?
  • Swapping activity as special case
  • correlation with pressure stall information (PSI)

eMPee584 avatar Oct 17 '23 10:10 eMPee584

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Feb 15 '24 01:02 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jun 15 '24 01:06 github-actions[bot]

Well ok the issue is stale yes, but it is not quite resolved. At the moment, to track disk I/O traffic and the source application, one has to combine multiple tools like diskgraph, nmon, iotop, fatrace, blktrace et cetera..

eMPee584 avatar Jun 30 '24 17:06 eMPee584