[slurm-users] How to track solver usage in Slurm

[fernando.seguro--- via slurm-users]

I don't see an easy way of tracking this in slurm. I tried using the --comment="slover" directive, but this gets mapped to the "derived_es" column in the database, which is reserved for job info on errors, from what I read.

This would make a good enhancement request. Where would I submit that?
Something like:
SBATCH --solver=fluent
or
SBATCH --solver=LSDyna

This would be very helpful for tracking solver usage without having to use the job-name. Great for reporting.
Please let me know if someone else has requested this previously.
If anyone has figured out a way to do it, please share.

thanks

--
slurm-users mailing list -- slurm...@lists.schedmd.com
To unsubscribe send an email to slurm-us...@lists.schedmd.com

[Davide DelVento via slurm-users]

You can create (fake or real) licenses for the applications you want to track and then use sreport to track their historical data. https://slurm.schedmd.com/licenses.html 

Pros:

- easy for you, it will take you few minutes to implement

- you may need/have that already in place if the software is licensed (if not, you can choose a number of licenses larger than the number of cores you have on your cluster and avoid artificially limiting concurrent jobs)

Cons:

- gotta convince users to use it, see my past messages about it on this list where I wanted to "hide" licensed software unless license was requested (spoiler alert, I found that too complicated and gave up)

- unless successful hiding binaries based on license request, users can still use it wrongly (not requesting them when needed), and in both case they can request "license" when not needed -- messing up your stats

Alternatively, you can make the real executables hidden and write wrapper scripts like this (and you may need an epilog to report "stopping" in case the job is cancelled, unless you do that separately from the JOBID data)

#!/bin/bash

LOG=make your own logic for how you want to store this (e.g. by user, date, etc)

date >> $LOG # you may want to use rfc or iso format for date

echo $USER is starting fluent in job $SLURM_JOBID >> $LOG

echo other info you may want to store >> $LOG

/full/hidden/path/to/fluent $@

echo $USER stopped fluent in job $SLURM_JOBID >> $LOG

[Cutts, Tim via slurm-users]

I would love to see something similar; some sort of relatively arbitrary tagging of jobs.  For example, a job might well be associated with a particular project – now to some extent you could use the ‘account’ mechanism for that, but flexible tagging is very useful in cloud settings, and would also be here.

 

Tim

---

AstraZeneca UK Limited is a company incorporated in England and Wales with registered number:03674842 and its registered office at 1 Francis Crick Avenue, Cambridge Biomedical Campus, Cambridge, CB2 0AA.

This e-mail and its attachments are intended for the above named recipient only and may contain confidential and privileged information. If they have come to you in error, you must not copy or show them to anyone; instead, please reply to this e-mail, highlighting the error to the sender and then immediately delete the message. For information about how AstraZeneca UK Limited and its affiliates may process information, personal data and monitor communications, please see our privacy notice at www.astrazeneca.com

[John Hearns via slurm-users]

There was a project at one of the US National Labs which might be relevant.

It involved placing a library in the library path of all jobs.

I remember talking with Rosemary Francis when she was at Ellexus, regarding commercial support for this project.

John Hearns