Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #261

Closed
Open
Created Dec 10, 2019 by Shane Snyder@ssnyderOwner

investigate Darshan deployment strategies for system's that dynamically link by default

Cori, Theta, and Summit will all use dynamic linking by default in the near future.

We should investigate deployment strategies at each facility to determine best way to support Darshan's shared library for programs on the compute nodes. This may just result in some best practices information being folded into documentation, but it's possible that we add some soft of mechanisms to Darshan to better support this.

Assignee
Assign to
Time tracking