[slurm-users] runtime priority

[Lawrence Stewart]

As far as I can tell, sbatch —nice only affects scheduling priority, not CPU priority.

I’ve made a workaround by putting “nice -n 19 xxx” as the job to run in my sbatch scripts

> On 2020, Jun 30, at 11:07 AM, Renfro, Michael <Renfro at tntech.edu> wrote:
> 
> There’s a --nice flag to sbatch and srun, at least. Documentation indicates it decreases priority by 100 by default.
> 
> And untested, but it may be possible to use a job_submit.lua [1] to adjust nice values automatically. At least I can see a nice property in [2], which I assume means it'd be accessible as job_desc.nice in the Lua script.
> 
> [1] https://github.com/SchedMD/slurm/blob/master/contribs/lua/job_submit.lua
> [2] https://github.com/SchedMD/slurm/blob/master/src/lua/slurm_lua.c
> 
>> On Jun 30, 2020, at 9:52 AM, Lawrence Stewart <stewart at serissa.com> wrote:
>> 
>> How does one configure the runtime priority of a job?  That is, how do you set the CPU scheduling “nice” value?
>> 
>> We’re using Slurm to share a large (16 core 768 GB) server among FPGA compilation jobs.  Slurm handles core and memory reservations just fine, but runs everything nice -19, which makes for hugh load averages and terrible interactive performance.
>> 
>> Manually setting the compilation processes with “renice 19 <pid>” works fine, but is tedious.
>> 
>> -Larry
>> 
>> 
>