On Saturday, 15 September 2018 12:25:18 AM AEST Jessica Nettelblad wrote:
> Anyone else hanging out in Madrid before Slurm User Group meeting? We're a
> bunch of people registered for SLUG who certainly will. Meet with us if you
> want to!
Would love to, but cannot attend for family reasons this
Ketiw,
Can this can be done in /etc/security/limits.conf file in your case?
F.e. '@users hard priority 10' will set default nice level for all users to 10
(and priority to 3. Default nice is 0 and priority is 20).
But keep in mind, if your Slurm is configured to enforce CPU core (cgroups?) ,
On Fri, Sep 14, 2018 at 02:34:10PM +0200, Loris Bennett wrote:
> Tim Bishop writes:
> > New member to the list, and we've only been using Slurm for a few
> > months. Everything is working well but I have some questions about user
> > management.
> >
> > Our setup is that users are managed via LDAP
So we figured out the problem with "slurmd -C": we had run rpmbuild on the
POWER9 node, but did not have the hwloc-package installed. The build
process looks for this, and if not found, will apparently note use
hwloc/lstopo even if installed post-build.
Now Slurm reports the expected topology for
A 'nice -n 19' process will still consume 100% of the CPU if nothing else is
going on.
‘top’ output from a dual-core system with 3 ‘dd’ processes -- 2 with default
nice value of 0, and 1 with a nice value of 19:
=
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
Anyone else hanging out in Madrid before Slurm User Group meeting? We're a
bunch of people registered for SLUG who certainly will. Meet with us if you
want to!
On Monday, September 24, around 5 pm, we're doing escape rooms at
http://exit-game.es/?lang=en (costs about €20). Then we're heading out f
Dear Dimitri,
Thank you for the answer. I was considering this but I would have to relay
on users to submit their jobs that way. I just found a simpler solution but
also somewhat limited in scope:
If
*PropagatePrioProcess* is set to 0 which is a default then the tasks will
inherit slurmd priority
Hi,
I'm trying to deploy slurm scheduler but I'm facing some issue with x11; I
got this error :
srun: error: Cannot forward to local display. Can only use X11 forwarding
with network displays.
when I try to launch a job from a slurm login to a slurm node.
Here some tests:
from notebook [NB] -> s
Hi Ketiw,
Wouldn't 'nice' work in this case?
$ man nice
...
NAME
nice - run a program with modified scheduling priority
SYNOPSIS
nice [OPTION] [COMMAND [ARG]...]
...
In your submit script you would run the program as
nice -n 19
-Original Message-
From: slurm-users O
kesim writes:
>> On Fri, Sep 14, 2018 at 2:41 PM Loris Bennett
>> wrote:
>>
>> Hi Ketiw,
>>
>> kesim writes:
>>
>> > Dear all,
>> >
>> > I would like to submit a job in such a way that the actual program is
>> > run with the lowest priority (nice=19 on linux). At the moment every
>> >
Hi Ketiw,
kesim writes:
> Dear all,
>
> I would like to submit a job in such a way that the actual program is
> run with the lowest priority (nice=19 on linux). At the moment every
> task has priority 0. Is it possible to do that and how?
>
> Best regards,
>
> Ketiw
I'm not aware that this is
Hi Tim,
Tim Bishop writes:
> Hi all,
>
> New member to the list, and we've only been using Slurm for a few
> months. Everything is working well but I have some questions about user
> management.
>
> Our setup is that users are managed via LDAP. They exist on all compute
> nodes and on the submis
Dear all,
I would like to submit a job in such a way that the actual program is run
with the lowest priority (nice=19 on linux). At the moment every task has
priority 0. Is it possible to do that and how?
Best regards,
Ketiw
Hi all,
New member to the list, and we've only been using Slurm for a few
months. Everything is working well but I have some questions about user
management.
Our setup is that users are managed via LDAP. They exist on all compute
nodes and on the submission node, but not on the controller (possib
14 matches
Mail list logo
