Re: Restrict jobs CPU usage

[Anton Gombkötö <Gombkoetoe@xxxxxxxxxx>]

Simon,

for the future discussions (performance discussions keep coming back like a
boomerang):

- watch the decrease of used CPU seconds. Run the job before you start
optimizing and write down the number of CPU seconds used. For batch jobs,
it's in the joblog's last message (CPF1164); for interactive jobs press F11
to see the column with the used CPU seconds (or use DSPJOB OPTION(*RUNA) to
see the value in ms). Your efforts should decrease this number, and that's a
fact that you can drop in every discussion. You can prove that your time
wasn't wasted.

- I try to explain the near 100%-CPU-dilemma like this: Imagine a gardener
watering flowers. When there is only one flower, this one uses 100% of the
gardeners time. The gardener will be finished earlier, of course. If there
are more flowers, each of them is using a smaller percentage of the
gardener's time. But it will be the same amount of water as before for each
flower, and it takes the gardener longer to water all of he flowers. (You
can decorate the story to explain the overhead of managing n1 jobs using
n2 CPU's :-)

And to respect the subject of this thread: CPU usage can be restricted to a
certain amount by changing the *CLS (class) object. When a job tries to use
more, it is ended, which is in the most cases worse than waiting...

0.02 Euro

Anton Gombkötö



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---