Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #191

Closed
Open
Opened May 27, 2016 by Philip Carns@carns
  • Report abuse
  • New issue
Report abuse New issue

eliminate shutdown timing skew

Right now there is nothing stopping one rank from beginning Darshan shutdown way before another one, which may cause Darshan to report an unusually high shutdown time.

The simplest fix is probably to add a barrier before timing begins in the Darshan shutdown routine. That routine will collectively synchronize shortly afterwards anyway.

Assignee
Assign to
3.1.0
Milestone
3.1.0
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: darshan/darshan#191