[slurm-users] Automatically setting OMP_NUM_THREADS=SLURM_CPUS_PER_TASK?

Ryan Novosielski novosirj at rutgers.edu
Tue Mar 6 16:13:18 MST 2018

Thanks, Martin — I almost mentioned Utah in my original e-mail as I turned up your support page in a search.

It is good to know definitively that MKL honors that variable — would be preferable to having to know about various different ones.

> On Mar 6, 2018, at 6:07 PM, Martin Cuma <martin.cuma at utah.edu> wrote:
> Ryan,
> we set OMP_NUM_THREADS=1 in the R and Python modules (MKL will honor that), and instruct those users that want to run multi-threaded to set OMP_NUM_THREADS themselves after loading the module - and make sure they don't oversubscribe the node.
> In our experience majority of R and Python users run independent serial calculations so the default OMP_NUM_THREADS=1 is reasonable.

|| \\UTGERS,  	 |---------------------------*O*---------------------------
||_// the State	 |         Ryan Novosielski - novosirj at rutgers.edu
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
||  \\    of NJ	 | Office of Advanced Research Computing - MSB C630, Newark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 236 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20180306/93325480/attachment.sig>

More information about the slurm-users mailing list