Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D darshan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • darshan
  • darshan
  • Issues
  • #306
Closed
Open
Issue created Mar 08, 2021 by Philip Carns@carnsOwner

add a "worst case" I/O cost per process graph to job-summary

The current darshan-job-summary pdf includes a graph that looks like the attachment Screenshot_from_2021-03-08_14-28-32. It shows the average I/O cost per process, which means summing up read, write, and metadata time across all ranks and dividing by the number of ranks.

This is helpful in many cases, but it fails to highlight cases where the application is held back by one rank (or a few ranks) spending more time in I/O than the others. The worst case would be a job that does "rank 0 I/O" (i.e., all I/O from a single process of the job). On average this would look fine in this graph if there are enough ranks not doing I/O to amortize the cost.

We should add an additional graph that at least shows the worst case rank in terms of I/O percentage in addition to the average percentage.

Assignee
Assign to
Time tracking