On Thu, 2020-08-06 at 09:30 -0400, Paul Raines wrote: > Bas > > Does that mean you are setting PriorityFlags=MAX_TRES ? > YES
> Also does anyone understand this from the slurm.conf docs: > > The weighted amount of a resource can be adjusted by adding a suffix of > K,M,G,T or P after the billing weight. For example, a memory weight of > "mem=.25" on a job allocated 8GB will be billed 2048 (8192MB *.25) units. A > memory weight of "mem=.25G" on the same job will be billed 2 (8192MB * > (.25/1024)) units. > > Where is this "2048" and "2" factor coming from in those two calculations? > job is using 8G --> 0.25 * 8192 = 2048 with .25G ---) .25/1024M --> 8192 * 0.25/1024 = 2 Memory is always a factor 1024 > On Thu, 6 Aug 2020 6:46am, Bas van der Vlies wrote: > > > Il 06/08/20 10:00, Bas van der Vlies ha scritto: > > > > Tks for the answer. > > > > > > We have also node with GPU's (dfiferent types) and some cost more the > > > > others. > > > The partitions always have the same type of nodes not mixed,eg: > > > * > > > TRESBillingWeights=CPU=3801.0,Mem=502246.0T,GRES/gpu=22807.0,GRES/gpu:tita > > > nrt > > > x=22807.0 > > > * node type: 24 cores 4 GPU's MemSpecLimit=1024 Memory=191488 > > > * the max is 91228 SBU > > Still missing something. Can't come to your result. > > 24*3801+502246*(191488-1024)/(1024**5)+4*22807 = 182452 (rounded), about > > twice your result. > > > > we have MAX(core, mem, gres). all resources can have the score: 91228 > > 24 * 3801 = 91224 > > mem same value > > 4 gres * 22807 = 91228 > > > > So we take one of these maximum values we dived it again by 1000 and round > > it. Hopefully this explains it. > > > > DIFA - Dip. di Fisica e Astronomia > > Servizi Informatici > > Alma Mater Studiorum - Università di Bologna > > V.le Berti-Pichat 6/2 - 40127 Bologna - Italy > > tel.: +39 051 20 95786 > > > >
smime.p7s
Description: S/MIME cryptographic signature
