You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I have some problems with some of my slurm jobs which gpu information are not well exported and I wonder if it might be related to slurm arrays...
Have you ever tested jobstats in such condiftions?
I mean with sbatch having such param:
#SBATCH --array=0-4
This creates jobids which are not integers anymore but rather something like this: $JOB_ID_0, $JOB_ID_1, $JOB_ID_2 and $JOB_ID_3
Any ideas?
Thx,
--Mike
The text was updated successfully, but these errors were encountered:
we use jobstats with GPU arrays regularly. Stats are collected with $SLURM_JOBID which is same as jobidraw in sacct. If you have it setup the way we recommend you can verify this by logging to a node where a GPU array job is running and checking /run/gpustat/X where X=GPU ordinal number (or GPU-UUID).
Hello,
I have some problems with some of my slurm jobs which gpu information are not well exported and I wonder if it might be related to slurm arrays...
Have you ever tested jobstats in such condiftions?
I mean with sbatch having such param:
#SBATCH --array=0-4
This creates jobids which are not integers anymore but rather something like this: $JOB_ID_0, $JOB_ID_1, $JOB_ID_2 and $JOB_ID_3
Any ideas?
Thx,
--Mike
The text was updated successfully, but these errors were encountered: