[slurm-users] Re: Slurm Reporting Difference between sreport and sacct

2025-05-23 Thread Paul Raines via slurm-users
But I also find things inconsistent with just sreport itself. I run: sreport -T Gres/gpu cluster Utilization Start=01/01/25 End=04/30/25 Allocated Down PLND Dow Idle Planned Reported - - -- 15310868 4511980 86073

[slurm-users] Re: Slurm Reporting Difference between sreport and sacct

2025-05-23 Thread Passant Hafez via slurm-users
Hi Steen, Thanks a lot, that certainly sorted out most of the discrepancies! I'm still having some differences though for the sreport and saact output for certain accounts so was wondering if there's anything else I'm missing in how sreport calculates it (for sacct I use cputimeraw and sum it a

[slurm-users] Re: Slurm Reporting Difference between sreport and sacct

2025-05-22 Thread Steen Lysgaard via slurm-users
Hi Passant, I've found that when using sacct to track resource usage over specific time periods, it's helpful to include the --truncate option. Without it, jobs that started before the specified start time will have their entire runtime counted, including time outside the specified range. The