ct' rather than sreport and get individual job data. That is
ingested into a db and PowerBI, which can then aggregate as needed.
sreport is pretty general and likely not the best for accurate
chargeback data.
Brian Andrus
On 3/4/2024 6:09 AM, Chip Seraphine via slurm-users wrote:
> He
Hello,
I am attempting to implement a billback model and finding myself stymied by
the way that sreport handles job arrays. Basically, when a user submits a
large array, their usage includes time that jobs in the back of the array spend
waiting their turn. (My #1 user in “sreport user topus
Hello,
TL,DR: How does the relative QOS flag work?
I have a QOS and I want it to be collectively restricted to 50% of the
reachable cores in the cluster. I’ve been managing this by dividing my core
count to 2 to get N, and doing ‘sacctmgr update qos foobar set MaxTRES=cpu=N’.
That’s fine,
Normally I'd address this by having an sbatch script allocate enough resources
for both jobs (specifying one node), and then kick off the helper as a separate
step (assuming I am understanding your issue correctly).
On 2/9/24, 9:57 AM, "Alan Stange via slurm-users"
mailto:slurm-users@lists.sc
