On 3/3/24 23:04, John Joseph via slurm-users wrote:
Is SWAP a mandatory requirement
All our compute nodes are diskless, so no swap on them.
--
Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an e
That's essentially what I've been doing-- a daily 'sacct' that dumps a json
file, and then I dig through the json files. I'm basically doing the same
thing that sreport is doing. Given the enormous amount of machinery in Slurm
for handling rollups, it seems bizarre that the whole thing is made
Chip,
I use 'sacct' 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
Joseph,
You will likely get many perspectives on this. I disable swap completely
on our compute nodes. I can be draconian that way. For the workflow
supported, this works and is a good thing.
Other workflows may benefit from swap.
Brian Andrus
On 3/3/2024 11:04 PM, John Joseph via slurm-user
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
It depends on a number of factors.
How do your workloads behave? Do they do a lot of fork()? I’ve had cases in
the past where users submitted scripts which initially used quite a lot of
memory and then used fork() or system() to execute subprocesses. This of
course means that temporarily (be
