Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding gpu aware mpi to osu-micro-benchmarks w/ rocm variant #581

Open
wants to merge 44 commits into
base: develop
Choose a base branch
from

Conversation

august-knox
Copy link
Collaborator

Description

Adding compatibility with gpu-aware mpi on rocm for osu-micro-benchmarks.
Tested with the following system description:
benchpark system init --dest=tioga-gtl llnl-elcapitan cluster=tioga +gtl

Adding/modifying a benchmark (docs: Adding a Benchmark)

  • (optional) If package upstreamed to Spack is insufficient, add/modify repo/benchmark_name/package.py
  • (optional) If application upstreamed to Ramble is insufficient, add/modify repo/benchmark_name/application.py
  • Tags in Ramble's application.py or in repo/benchmark_name/application.py will appear in the docs catalogue
  • Add/modify an experiments/benchmark_name/experiment.py to define a single node and multi-node experiments
  • Add/modify a dry run unit test in .github/workflows/run.yml

@august-knox august-knox requested a review from nhanford January 28, 2025 18:19
@github-actions github-actions bot added experiment New or modified experiment ci CI, unit tests, GitHub actions labels Jan 28, 2025
@august-knox august-knox changed the title Osu micro benchmarks Adding gpu aware mpi to osu-micro-benchmarks w/ rocm variant Jan 28, 2025
env.prepend_path("PATH", join_path(mpidir, "one-sided"))
env.prepend_path("PATH", join_path(mpidir, "collective"))
if self.spec.satisfies("+rocm"):
env.prepend_path("LOCAL_RANK", "$MV2_COMM_WORLD_LOCAL_RANK")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@august-knox Is this variable system/mpi specific or application-specific?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rfhaque It's an application-specific variable used to identify the process rank on a node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
application ci CI, unit tests, GitHub actions experiment New or modified experiment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants