Thank you so much.. already started working ..little optimized a bit ..
Thanks again!
*sacct --format=user,ncpus,state,elapsed --starttime=04/1/17
--endtime=03/31/18 | grep COMPLETED | grep mithunr | awk '{print $4}'
*
Thanks & Regards,
Sudeep Narayan Banerjee
On 12/04/20 5:43 am, Pablo
You can optimize your query as follows
[root@hpc ~]# sacct --format=user,ncpus,state,elapsed --starttime=01/1/20
--endtime=03/31/20 --state=COMPLETED -u mithunr
El sáb., 11 abr. 2020 a las 11:37, Sudeep Narayan Banerjee (<
snbaner...@iitgn.ac.in>) escribió:
> Dear Michael: Thank you, I also
Dear Michael: Thank you, I also did the same now and seems to work !!!
Thanks
[root@hpc ~]# sacct --format=user,ncpus,state,elapsed
--starttime=01/1/20 --endtime=03/31/20 | grep COMPLETED | grep mithunr
mithunr 32 COMPLETED 1-12:36:02
mithunr 32 COMPLETED 1-08:36:56
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.
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
