Some more hints on where to look for regarding the functional policy:
* You probably will want to set auto_user_fshare in the cluster config.
* You probably will want to set share_functional_shares in the
scheduler config
* Then use the weighting in the scheduler config to determined the
Oh ... and you can also mix the functional with the fairshare policy ...
Fritz
Fritz Ferstl schrieb:
I'm always interested ;-) - hence I'm still involved after more than
20 years ...
As I wrote, I'd look into the functional policy.
Or if you are using fairshare, as Chris writes, then you mig
I'm always interested ;-) - hence I'm still involved after more than 20
years ...
As I wrote, I'd look into the functional policy.
Or if you are using fairshare, as Chris writes, then you might be able
to mix this through the weighting with the -p prio to get something
similar to what you wan
Yep I think we are going to try this and monitor it. Gut feeling is that
the fairshare by user policy has so much more impact/weight on the
global job waitlist that if we just have a single user doing stuff with
"-p -10" and "-p -1" to distinguish between her own jobs it might
actually do cl
> Am 30.04.2015 um 18:21 schrieb Chris Dagdigian :
>
>
> GE and UGE man pages are not clear about the scope of "-p" priority values
> when a user uses it. It's been a long time since I needed this and I wanted
> to confirm the scope of the behavior ..
>
> Use case:
>
> - I need to submit 100
On Thu, 30 Apr 2015, Fritz Ferstl wrote:
Nah, the weight_priority won't help. It just determines how much influence
the -p has vs things like job wait time or urgency. If you have none of those
then all being equal it would have the same effect as if you left it
untouched. And if you have infl
Nah, the weight_priority won't help. It just determines how much
influence the -p has vs things like job wait time or urgency. If you
have none of those then all being equal it would have the same effect as
if you left it untouched. And if you have influence from waiting time or
urgency or othe
Hi Chris,
if memory serves correctly then the so called POSIX priority is one
range applied to all jobs. So you would be penalizing your jobs.
If you need this more often then you could either ensure that jobs
always are submitted with a negative priority (say -100) and then
regular users ha
On Thu, 30 Apr 2015, Chris Dagdigian wrote:
...
- Does my use of "-p" to send lower-than-zero values for my submitted jobs
affect just MY jobs and the order in which they get dispatched or will I end
up penalizing myself globally because all the other jobs from other users on
the cluster are ru
GE and UGE man pages are not clear about the scope of "-p" priority
values when a user uses it. It's been a long time since I needed this
and I wanted to confirm the scope of the behavior ..
Use case:
- I need to submit 100 personal jobs as "dag" with 10 jobs being
slightly more important
10 matches
Mail list logo
