I'll see what options the user provided but I do believe he tried this combo. We also found that someone else had this issue felt it was a bug but no one responded to his original issue. But other conversations started up in the thread.
Thanks Jackie Scoggins > On Jun 9, 2015, at 6:57 PM, Christopher Samuel <[email protected]> wrote: > > > Hiya Jacqueline! > >> On 10/06/15 10:51, Jacqueline Scoggins wrote: >> >> First round of testing cgroups and noticed that no matter how many cpus >> requested (-n x) the users job is only running on one cpu. > > -n is tasks, -c is CPUs per task. > > For our users doing SMP jobs we suggest they do: > > #SBATCH --ntasks=1 > #SBATCH --cpus-per-task=x > > So they understand that they are running a single process that needs 'x' > cores. > > Best of luck! > Chris > -- > Christopher Samuel Senior Systems Administrator > VLSCI - Victorian Life Sciences Computation Initiative > Email: [email protected] Phone: +61 (0)3 903 55545 > http://www.vlsci.org.au/ http://twitter.com/vlsci
