Philip Kovacs writes:
>>according to https://slurm.schedmd.com/mpi_guide.html I have built
>>Slurm 19.05 with PMIx support enabled and it seems to work for both,
>>OpenMPI and Intel MPI. (I've also set MpiDefault=pmix in slurm.conf.)
>
>>But I still don't get the point. Why should I favour `srun
>according to https://slurm.schedmd.com/mpi_guide.html I have built
>Slurm 19.05 with PMIx support enabled and it seems to work for both,
>OpenMPI and Intel MPI. (I've also set MpiDefault=pmix in slurm.conf.)
>But I still don't get the point. Why should I favour `srun ./my_mpi_program´
>over `mpi
One other thing I noticed is that the contents of the *_job_table has
entries in tres_alloc and tres_req that seem to match types in the
tres_table, but there are no mem entries.
For example, tres_table=
+---+-+--++--+
| creation_time | deleted | id | t
I have
JobAcctGatherType = jobacct_gather/linux
Brian
On Mon, Sep 16, 2019 at 12:40 PM Antony Cleave
wrote:
> Just a quick thought.
>
> What is your slurm.conf setting for this?
>
> *JobAcctGatherType* is operating system dependent and controls what
> mechanism is used to collect accounti
Dear all,
according to https://slurm.schedmd.com/mpi_guide.html I have built
Slurm 19.05 with PMIx support enabled and it seems to work for both,
OpenMPI and Intel MPI. (I've also set MpiDefault=pmix in slurm.conf.)
But I still don't get the point. Why should I favour `srun ./my_mpi_program´
ove
Just a quick thought.
What is your slurm.conf setting for this?
*JobAcctGatherType* is operating system dependent and controls what
mechanism is used to collect accounting information. Supported values are
*jobacct_gather/linux* (recommended), *jobacct_gather/cgroup* and
*jobacct_gather/none* (no
Tim Wickberg writes:
> Thanks for the reminder. The final version is online now.
Thanks!
> (The only important change is that the time for dinner has been filled
> in, and the schedule is no longer marked as preliminary.)
Hey, Squatters Pub! I was actually considering it for dinner tonight. :)
Thanks for the reminder. The final version is online now. (The only
important change is that the time for dinner has been filled in, and the
schedule is no longer marked as preliminary.)
See you folks tomorrow!
- Tim
On 9/16/19 8:53 AM, Bjørn-Helge Mevik wrote:
The agenda on https://slurm.sc
I want to use --ntasks-per-socket flag to control how processes in a
multi-threaded application map to numa domains on the Cray system
cori[1]. In its haswell partition this system has 2 sockets per node.
The flag has no affect and the examples in the slurm docs[2] don't work
as described the
The agenda on https://slurm.schedmd.com/slurm_ug_agenda.html is still
called "Preliminary Schedule", and has not been updated since July 19.
Is this the latest agenda, or is there a newer one somewhere?
--
Regards,
Bjørn-Helge Mevik, dr. scient,
Department for Research Computing, University of O
Yep, the maxrss field is always blank.
I just checked on a different cluster and have the same result. Jobs
that completed last week even have nothing in that field.
So how can I troubleshoot this? Is there a way to log the sql queries
made by slurmdbd?
Brian
On 9/15/2019 10:29 PM, Christo
11 matches
Mail list logo