Sadly I don't have any deeper insight into the C API for that information.
-Paul Edmon-
On 11/3/2024 2:14 AM, Bhaskar Chakraborty wrote:
Hi Paul,
Thanks for the tip. Looking at the code it seems to compare each job’s
priority
variable through its job_ptr.
I did some experiments where I log the priority variable in job_ptr
for successive jobs submitted from same user.
However, I find them equal and so they don’t reflect the
first-come-first-serve order of the jobs.
Is there any other way through C APIs to gather the dynamic priority?
If we can at least find the start and end of a scheduling iteration
then it can help us
as we can evaluate the relative order of scheduling ourselves, but
this is more of a 2nd best solution or a workaround.
-Bhaskar.
Sent from Yahoo Mail for iPad
<https://mail.onelink.me/107872968?pid=nativeplacement&c=Global_Acquisition_YMktg_315_Internal_EmailSignature&af_sub1=Acquisition&af_sub2=Global_YMktg&af_sub3=&af_sub4=100000604&af_sub5=EmailSignature__Static_>
On Tuesday, October 29, 2024, 7:43 PM, Paul Edmon via slurm-users
<slurm-users@lists.schedmd.com> wrote:
If you are looking to use the C API for this then showq may be a
good guide: https://github.com/fasrc/slurm_showq
<https://github.com/fasrc/slurm_showq> The -o option orders the
pending queue in priority order.
If you are looking at native slurm commands, sprio can print out
the current priority breakdown of any job and filter by partition,
then you can reorder based on that. squeue also can print out
current priority. You might also look at the --priority option:
https://slurm.schedmd.com/squeue.html#OPT_priority
<https://slurm.schedmd.com/squeue.html#OPT_priority>
-Paul Edmon-
On 10/29/24 9:33 AM, Bhaskar Chakraborty via slurm-users wrote:
Hello,
Is there any DS in slurmctld which portrays the dynamic relative
priority of pending jobs?
We are trying to use slurm for developing a scheduling solution
and 1 of the problems we face at the outset is how to determine
the order of scheduling for pending jobs.
One option is to find scheduling iteration window begin & close
pointers & cache the job ids as seen in order & then make them the
priority order at that point of time.
( This means for 500 pending jobs, say, if we can find which are
the slurmctld calls which mark the beginning & end of a sched
iteration then we can use the scheduling order
of jobs as the relative priority order for that period of time, of
course it may change depending on fairshare, user initiated
priority modification etc. )
A concrete existing data structure showing the dynamic priority
itself from slurmctld would be handy.
Help appreciated.
Thanks!
Bhaskar.
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
