Thanks, Kelly, I will test this. Do you have any more specifics on how things may misbehave with this setup?
On Tue, Jan 5, 2016 at 6:42 PM, <[email protected]> wrote: > Hi Kris, > You can use the environment variable SLURM_HINT=nomultithread and that > will default to not using multithreads. You can set that up for all users > and if they choose to use multithreads they can use the --hint=multithread > option on the command line. Be careful as we have found in some later > versions (> 14.11.9) this may not work as expected and will the > multithreads. This could all depend on configuration. > Kelly > > > On 01/05/16, Kris Kersten<[email protected]> wrote: > > I'm trying to better understand the use of SLURM with hyperthreads. On a > system with hyperthreads enabled (i.e., in BIOS), by default SLURM presents > all hyperthreads to a user application. The user can restrict an > application to using a single hyperthread per core with the srun > --hint=nomultithread option. > > The documentation also states that the reverse is possible, that a user > can request to use all hyperthreads per core by calling srun > --hint=multithread. What I can't find is a configuration option to make > the --hint=nomultithread behavior the default, so that multiple > hyperthreads per core are made available only when specifically requested > with --hint=multithread. Is this possible? something in slurm.conf? or > elsewhere? > > Thanks, > Kris > >
