Unless I’m misreading it, you have a wall time limit of 2 days, and jobs that use up to 32 CPUs. So a total CPU time of up to 64 CPU-days would be possible for a single job.
So if you want total wall time for jobs instead of CPU time, then you’ll want to use the Elapsed attribute, not CPUTime. -- Mike Renfro, PhD / HPC Systems Administrator, Information Technology Services 931 372-3601<tel:931%20372-3601> / Tennessee Tech University On Apr 11, 2020, at 10:05 AM, Sudeep Narayan Banerjee <snbaner...@iitgn.ac.in> wrote: Hi, I want to calculate the total walltime or runtime for all jobs submitted by each user in a year. I am using the syntax as below and it is also generating some output. We have walltime set for queues (main & main_new) as 48hrs only but the below is giving me hours ranging from 15hrs to 56 hours of even more. I am missing anything from logical/analytical point of view or the syntax is not correct with respect to the desired information ? Many thanks for any suggestion. [root@hpc ~]# sacct --format=user,ncpus,state,CPUTime --starttime=04/01/19 --endtime=03/31/20 | grep mithunr mithunr 32 COMPLETED 15-10:34:40 mithunr 16 COMPLETED 00:02:56 mithunr 16 COMPLETED 02:22:40 mithunr 16 COMPLETED 00:00:48 mithunr 16 COMPLETED 00:00:32 mithunr 16 FAILED 00:00:32 mithunr 16 FAILED 00:00:32 mithunr 16 FAILED 00:00:48 mithunr 16 FAILED 00:00:32 mithunr 16 FAILED 00:00:32 mithunr 0 CANCELLED+ 00:00:00 mithunr 16 FAILED 00:00:32 mithunr 32 COMPLETED 00:02:08 mithunr 0 CANCELLED+ 00:00:00 mithunr 32 COMPLETED 00:01:36 mithunr 16 FAILED 00:00:48 mithunr 32 COMPLETED 33-02:58:08 mithunr 32 COMPLETED 56-01:23:12 ....................... ...................... ...................... -- Thanks & Regards, Sudeep Narayan Banerjee System Analyst | Scientist B Information System Technology Facility Academic Block 5 | Room 110 Indian Institute of Technology Gandhinagar Palaj, Gujarat 382355 INDIA
