Job Runtime - Monitor and Profile
When a job is running through a vovtasker, the tasker automatically monitors RAM and CPU utilization of the job, including all of its children.
Job statistics are sampled about once a minute. This data sampling rate does not capture jobs that complete in less time than the than the sampling period.
The MAXRAM is expressed in Megabytes (MB), where 1MB = 1<<20 bits (left-shift decimal "1" 20 times is the binary equivalent of 1 million. The CPU time is stored in ms (milliseconds), but is expressed in s (seconds).
CPU Progress and Run Status Indicators
Accelerator Plus monitors CPU and RAM utilization for all
the running jobs. The CPU utilization information is available in four fields:
- CPUTIME
- The total accumulated CPU time in milliseconds.
- CPUPROGRESS
- Percentage of CPU accumulated in the unit time. For example, if in 60 seconds a job uses 60 seconds of CPU time, then the CPUPROGRESS is going to be 100. This field can be 0 (zero) for jobs that are stuck: holding onto the CPU resource but not running, which makes the CPU unavailable for other jobs. This field can also be greater than 100 for multi-threaded jobs.
- LASTCPUPROGRESS
- A timestamp indicating the last time CPU usage has increased. This is used to identify stuck jobs.
- RUNSTATUS
- A descriptive text field that shows how well the job is doing. Some typical values are Good, Paging, NoCpu. The complete list of values is shown below.
| n/a | Insufficient information to determine CPU progress. Typical for jobs that have just started. |
| Good | The progress is greater than 70% |
| Medium | Progress is between 10% and 70% |
| Poor | Less than 10% CPU utilization, but no swapping of pages. |
| Paging | The progress is less than 10% and the job is swapping at a rate greater than 1000 pages per second. |
| NoCpu | The job is not accumulating any CPU time. |
| Susp | The job is suspended. |