Hi Ulf, You may want to take a look at adjusting bf_max_job_test and depending on your typical runtime for jobs increasing bf_resolution to combat an increase in overhead.
On 08/22/2016 10:24 AM, Ulf Markwardt wrote: > Dear all, > > how can I bring the backfill scheduler to examine all low-priority jobs > for possible execution? > > We have situations with >100000 jobs and times with just a few hundreds. > So a fixed bf_interval does not make sense. > > Is there some option to say the bf scheduler runs down to the bottom of > the queue an then starts at the top, just ignoring bf_interval. > > As a workaround, I now have a python script checking sdiag (via API). If > "Last depth cycle" is much smaller than "Last queue length" I increase > bf_interval by 50% (+ scontrol reconf) - and the other way round > comparing the bf cycle time with bf_interval. > This works but I would assume something built-in in Slurm - though I > haven't found it, yet. > > Best, > Ulf > > > > -- Daniel M. Weeks Senior Systems Administrator Center for Computational Innovations Rensselaer Polytechnic Institute Troy, NY 12180 518-276-4458
