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

For GPU nodes, include scaling within a single node across GPUs #179

Open
jkoefinger opened this issue Nov 30, 2022 · 2 comments
Open

For GPU nodes, include scaling within a single node across GPUs #179

jkoefinger opened this issue Nov 30, 2022 · 2 comments

Comments

@jkoefinger
Copy link
Member

Expected behavior

For benchmarking GPU nodes, one would want to scale across 1, 2, .... GPUs of a single node and then over multiple nodes. Some simulations might produce higher cumulative performance if simulations run on single GPUs or if simulations are only parallelized over some of the GPUs of a single node. Ideal scaling should go through the origin and a single GPU in this case.

Actual behavior

MDBenchmark only scales across different number of nodes. Thus, results can be misleading as explained above.

Your version of MDBenchmark:

(run mdbenchmark --version on your machine)

@balazsfabian
Copy link

Proposed layout for 'multidir' scaling plots

The left axis shows the individual (per system, blue circles) and cumulative performance (green crosses), while the left axis shows the performance relative to the 1GPU & 1 system case. Notes:

  • Gromacs requires ranks to be a multiple of the number of simulations. Here, they were set equal.
  • In all cases, the maximum allowed threads gave the best performance. Still, the optimal combination should be tested.
  • All possible interactions of the Martini test system (no PME!) were offloaded to gpu using
    srun gmx_mpi mdrun -nb gpu -bonded gpu -v -maxh 0.25 -resethway -noconfout -deffnm topol

performance-figure0-1

@jkoefinger
Copy link
Member Author

I made a separate issue for multidir scaling plots.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants