Chapter 2. Overview of job waits and iDoctor for iSeries Job Watcher 27
Here is an example to explain the considerations just discussed:
A batch job runs for 6 hours and uses 117 minutes of CPU. The first thing to consider is how
much of the wasted 243 minutes of elapsed time was spent in CPU queuing (that is,
contending or waiting for a processor). This chapter demonstrates how this value, and all the
waits, can be measured in great detail. But for this example, we suppose that 71 minutes of
CPU queuing was involved. This means that the job was in type B waits 172 minutes. This
means that the job could potentially run in 3 hours and 8 minutes ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
Julian F.
Head of Cybersecurity
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
Addison B.
Field Engineer
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
Amir M.
Data Platform Tech Lead
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.