From https://slurm.schedmd.com/tres.html
"If TRESBillingWeights is not defined then the job is billed against the total number of allocated CPUs." You're probably getting the default behavior because your TRESBillingWeights string is invalid and isn't getting parsed properly -- see the trailing "G" on the Mem= specification? > On Feb 16, 2017, at 10:32 AM, Tomislav Subic <[email protected]> wrote: > > > Hi everyone, > > I have a question regarding the TRESBillingWeights option and the calculation > of used resources. I get how it works, and for things like CPU and memory the > behavior is expected, as described in the docs. In our setup we would like to > track Node-hours for each user. > > I configured the partition like this: > TRESBillingWeights="CPU=0.0,Node=1.0,Mem=0.0G" > > I expected that for a 1 minute job on the whole node, there would be added 1 > TRES to the users used resources, but instead 28 is added, which is the > number of cores on the node. Is this how it is intended to be, or is it a > bug? The docs don't mention anything about how the node option is billed. > > Thanks > > -- > Tomislav Šubić > Arctur d.o.o. :::::::::::::::::::::::::::::::::::::::::::::::::::::: Jeffrey T. Frey, Ph.D. Systems Programmer V / HPC Management Network & Systems Services / College of Engineering University of Delaware, Newark DE 19716 Office: (302) 831-6034 Mobile: (302) 419-4976 ::::::::::::::::::::::::::::::::::::::::::::::::::::::
