# Elapsed wall time in a parallel job using qstat
**URL:** https://community.openpbs.org/t/elapsed-wall-time-in-a-parallel-job-using-qstat/3279
**Category:** Users/Site Administrators
**Created:** [September 14, 2022, 4:27pm UTC](https://community.openpbs.org/t/elapsed-wall-time-in-a-parallel-job-using-qstat/3279 "2022-09-14T16:27:41Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Blackest](https://community.openpbs.org/u/Blackest)
#### Post date: [September 14, 2022, 4:27pm UTC](https://community.openpbs.org/t/elapsed-wall-time-in-a-parallel-job-using-qstat/3279/1 "2022-09-14T16:27:41Z")
Greetings,
As the title suggest, I would like to obtain the elapsed wall time from qstat when dealing with a parallel job. I tried using different options such as “qstat -s”, but the printed value for Elapsed Time is not right (I think it is multiplied by the number of cores). It also update quite slowly (at least every 10 seconds I would say).
Another issue I have, is the printed requested time. It shows the values set in the “resources\_max.cput” for the queue and not the one I set in the job file with “#PBS-l walltime”
Thank you!
---
### Author:  [@dtalcott](https://community.openpbs.org/u/dtalcott)
#### Post date: [October 3, 2022, 6:41pm UTC](https://community.openpbs.org/t/elapsed-wall-time-in-a-parallel-job-using-qstat/3279/2 "2022-10-03T18:41:07Z")
As you’ve probably figured out, if a job sets a limit on cput (either directly or from a queue default), that is what qstat reports. When no cput limit is given, qstat reports wall time.
As to the slow updating, this is to reduce load on execution hosts. See section 3.1.2.2 Polling on Linux in the Admin Guide if you want to tune the MoM differently.
---
### Author:  [@Source](https://community.openpbs.org/u/Source)
#### Post date: [July 17, 2023, 7:49am UTC](https://community.openpbs.org/t/elapsed-wall-time-in-a-parallel-job-using-qstat/3279/3 "2023-07-17T07:49:24Z")
maybe you want take a look at qstat -a?