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

Scripted Multi-tenancy on Hopper #2

Open
jrhaberstroh opened this issue May 24, 2013 · 1 comment
Open

Scripted Multi-tenancy on Hopper #2

jrhaberstroh opened this issue May 24, 2013 · 1 comment

Comments

@jrhaberstroh
Copy link
Owner

No implementation of cluster_traj_all for hopper, partly because multitenancy is unavailable, and 24 cores is excessive for most jobs. Figuring out how to do multi-tenancy jobs on hopper would be a boon.

@jrhaberstroh
Copy link
Owner Author

http://www.gromacs.org/Documentation/Acceleration_and_parallelization

Locking threads to physical cores
By default thread-MPI and the OpenMP parallelization, active when the verlet cut-off scheme is used, fill up all cores in the machine. When all cores used, mdrun will pin the threads to specific cores, if this hasn't already been done by MPI or OpenMP. If you want optimal performance when not using all cores, you need to use mdrun -pin on. If you want to run multiple jobs on the same compute node, you need to limit the number of cores used and if you want good performance, pin different jobs to different cores. The mdrun option -nt sets the total number of threads for an mdrun job. The -pinoffset option sets a pinning offset, counted in logical numbers of cores. For example, running 2 mdrun jobs on an Intel CPU with 6 physical cores with hyper-threading (supporting 2 threads) can be achieved with:

mdrun -nt 6 -pin on -pinoffset 0
mdrun -nt 6 -pin on -pinoffset 3

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

1 participant