[slurm-dev] slurm-dev Memory accounting issues with mpirun (was Re: Open-MPI build of NAMD launched from srun over 20% slowed than with mpirun)

2013-08-07 Thread Christopher Samuel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/07/13 17:06, Christopher Samuel wrote: Bringing up a new IBM SandyBridge cluster I'm running a NAMD test case and noticed that if I run it with srun rather than mpirun it goes over 20% slower. Following on from this issue, we've found

[slurm-dev] Re: slurm-dev Memory accounting issues with mpirun (was Re: Open-MPI build of NAMD launched from srun over 20% slowed than with mpirun)

2013-08-07 Thread Christopher Samuel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/08/13 16:19, Christopher Samuel wrote: Anyone seen anything similar, or any ideas on what could be going on? Sorry, this was with: # ACCOUNTING JobAcctGatherType=jobacct_gather/linux JobAcctGatherFrequency=30 Since those initial tests

[slurm-dev] Re: slurm-dev Memory accounting issues with mpirun (was Re: Open-MPI build of NAMD launched from srun over 20% slowed than with mpirun)

2013-08-07 Thread Janne Blomqvist
On 2013-08-07 09:19, Christopher Samuel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/07/13 17:06, Christopher Samuel wrote: Bringing up a new IBM SandyBridge cluster I'm running a NAMD test case and noticed that if I run it with srun rather than mpirun it goes over 20% slower.

[slurm-dev] Re: slurm-dev Memory accounting issues with mpirun (was Re: Open-MPI build of NAMD launched from srun over 20% slowed than with mpirun)

2013-08-07 Thread Christopher Samuel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/08/13 16:59, Janne Blomqvist wrote: That is, the memory accounting is per task, and when launching using mpirun the number of tasks does not correspond to the number of MPI processes, but rather to the number of orted processes (1 per

[slurm-dev] Re: 2.6.0 html documentation says CR_Core_Memory Not yet implemented

2013-08-07 Thread Moe Jette
That was old documentation. We'll fix that with the next web page update. Quoting Jeff Tan jeffe...@au1.ibm.com: Dear SchedMD, Just verifying what might be no more than a missed docupdate: is CR_Core_Memory definitely implemented in 2.6.0? The cons_res.html that comes with it says it

[slurm-dev] Re: cons_res: Can't use Partition SelectType

2013-08-07 Thread Eva Hocks
Hi Magnus, Thanks for the reply. I am using slurm.conf: SelectTypeParameter=CR_CPU_Memory to manage memory on the nodes. I am using partition.conf: SelectTypeParameter=CR_Core in one partition to allow gpu jobs to run without memory problems. The documentation states that is a valid set

[slurm-dev] Re: slurm-dev Memory accounting issues with mpirun (was Re: Open-MPI build of NAMD launched from srun over 20% slowed than with mpirun)

2013-08-07 Thread Danny Auble
Just a note, if srun isn't used to launch a task the odds of accounting for the step being correct are very low. Using srun is the only known way to always guarantee accounting for steps to be accurate. This also goes for handling memory limits. Danny On 08/07/13 00:43, Christopher

[slurm-dev] Re: Jobs not queued in SLURM 2.3

2013-08-07 Thread José Manuel Molero
Hi Carles, Thanks for your reply. I dont see any error in the logs files. I use -v flag and there arent errors. Thanks for your explain about backfillI used backfilling because it was the default option, but I had to eliminate the walltime limits due to some user complaints. This strange

[slurm-dev] Increase user priority on a specific partition

2013-08-07 Thread Neil Van Lysel
Hello, Is there a way to increase a users priority on a specific partition without using qos? When this user runs jobs on this partition I want their jobs to have a greater priority than all of the other jobs on this partition. Thanks for your help, Neil Van Lysel smime.p7s Description:

[slurm-dev] Re: slurm-dev Memory accounting issues with mpirun (was Re: Open-MPI build of NAMD launched from srun over 20% slowed than with mpirun)

2013-08-07 Thread Christopher Samuel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Danny, On 08/08/13 04:08, Danny Auble wrote: Just a note, if srun isn't used to launch a task the odds of accounting for the step being correct are very low. Using srun is the only known way to always guarantee accounting for steps to be