Hi Reuti,
Thanks William. In fact, yes, someone (Arnau) told me that he is doing
something like that with JSV files and the priority option. I think this is
the best solution for us. Not so hard to do and easy to manage.
Thanks for your help !
Cheers,
Remy
2016-06-28 17:48 GMT+02:00 Reuti <re...@staff.uni-marburg.de>:
> Hi,
>
> > Am 09.06.2016 um 17:53 schrieb Rémy Dernat <remy...@gmail.com>:
> > Hi,
> >
> > I am working on a way to prioritize jobs from some users on some
> specific queues. I know it can be done, but I do not know exactly how.
>
> As SGE will select a queue for your job according to the job requirements,
> it would be better to implement it in another way: by using a forced
> boolean or string complex with an attached urgency.
>
> Special users can then request this complex (either by theirselfs or by an
> JSV automatism) which must also be attached to a queue of your choice.
>
> -- Reuti
>
>
> > I saw that there's already "weight_user", but this value, combined with
> others must not exceed "1".
> >
> > Correct me if I am wrong, but the best way is to create a userset for
> these users and then apply a resource quota on it:
> >
> > e.g.:
> > {
> > name powerusers_on_testqueue
> > description "limit the priority for queue test.q for all users
> except for powerusers"
> > enabled TRUE
> > limit users {!@powerusers} queues {test.q} to weight_user=0.15
> > }
> >
> > The "powerusers" userset then would have a default weight_user of 0.25
> and would be prioritize over other users. There is also the fshare value on
> userset which could be modified.
> >
> > What do you think about it ? Is there a better way ? What are the best
> practice for this kind of stuff ?
> >
> >
> > Thanks,
> >
> > Cheers,
> > Rémy
> >
> >
> > _______________________________________________
> > users mailing list
> > users@gridengine.org
> > https://gridengine.org/mailman/listinfo/users
>
>
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
