Raw usage is a long double and the time added by jobs can be off by a
few seconds. You can take a look at _apply_new_usage() in
src/plugins/priority/multifactor/priority_multifactor.c to see exactly
what happens.
Ryan
On 11/25/2014 10:34 AM, Roshan Mathew wrote:
Hello SLURM users,
http://slurm.schedmd.com/sshare.html
*Raw Usage*
The number of cpu-seconds of all the jobs that charged the account by
the user. This number will decay over time when PriorityDecayHalfLife
is defined.
I am getting different /RAW Usage/ values for the same job every time
it is executed. The Job am using is a CPU stress test for 1 minute.
It would be very useful to understand the formula for how this RAW
Usage is calculated when we are using the plugin
PriorityType=priority/multifactor.
Snip of my slurm.conf file:-
# Activate the Multi-factor Job Priority Plugin with decay
PriorityType=priority/multifactor
# apply no decay
PriorityDecayHalfLife=0
PriorityCalcPeriod=1
PriorityUsageResetPeriod=MONTHLY
# The larger the job, the greater its job size priority.
PriorityFavorSmall=NO
# The job's age factor reaches 1.0 after waiting in the
# queue for 2 weeks.
PriorityMaxAge=14-0
# This next group determines the weighting of each of the
# components of the Multi-factor Job Priority Plugin.
# The default value for each of the following is 1.
PriorityWeightAge=0
PriorityWeightFairshare=100
PriorityWeightJobSize=0
PriorityWeightPartition=0
PriorityWeightQOS=0 # don't use the qos factor
Thanks!
