On Fri, Jan 31, 2020 at 06:26:19PM +0100, Reuti wrote: > > > > Am 31.01.2020 um 18:23 schrieb Jerome IBt <jer...@ibt.unam.mx>: > > > > Le 31/01/2020 à 10:19, Reuti a écrit : > >> Hi Jérôme, > >> > >> Personally I would prefer to keep the output of `qquota` short and use it > >> only for users's limits. I.e. defining the slot limit on an exechost basis > >> instead. This can also be done in a loop containing a command line like: > >> > >> $ qconf -mattr exechost complex_values slots=16 node29 > >>
> >> My experience is, that sometime RQS are screwed up especially if used in > >> combination with some load values (although $num_proc is of course fixed > >> in your case). > >> > >> -- Reuti > >> Dear Reuti, > > > > If i understand correctly, you recomend me to disable the RQS for the > > case of core, and add a complex_value of slots for all of the computes > > nodes? > > Exactly. Doing it on the command line within a loop is not so laborious and > it's a fixed feature of a node which will never change during its lifetime. > You don't even really need the loop as such. qconf -mattr will take multiple hostnames. I tend to feed it arguments with xargs eg: qhost -l status=POLICYOFF |xargs -r qconf -mattr exechost complex_values status=OK William
signature.asc
Description: PGP signature
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
