Re: Restrict jobs CPU usage

[Rob Berendt <rob@xxxxxxxxx>]

Uh gee, our main production box rarely even PEAKS at 40%.  However 
we will be doubling the processors from 4 to 8 next weekend.  Currently:
% CPU used . . . . . . . :        2.3
It's a management commitment issue.




songbird@sumter.net on 03/30/2000 05:09:20 PM
Please respond to RPG400-L@midrange.com@Internet
To:     RPG400-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: Restrict jobs CPU usage

We usually try and keep CPU usage at 70-80%. We have a lot of interactive
jobs running at the same time (taking phone orders from customers).
Of course if you have a heavy conversion program or batch job that wants to
hog CPU, you can create a separate pool for jobs that have to run
immediately. Change priority on any low priority batch job that seems to be
piggy. Use WRKACTJOB to see who the offending members are.
Do a WRKSYSSTS and check out % of ASP (Aux Storage Pool) that is being used.
Our CPU may look maxed out, but if the % of ASP is acceptable, then you
don't have to worry.
Look at the Wait-Inel (wait to ineligible) column on the WRKSYSSTS screen
again. If the pools are below 10%, all is well. Otherwise, adjust the MAX
Act column for the pool in question until it comes down to under 2%.
Check out the red book "AS/400 Performance Management " for exact numbers
for these settings and a better explanation.
..
C.A.


----- Original Message -----
From: John Hall <jhall@hillmgt.com>
To: <RPG400-L@midrange.com>
Sent: Thursday, March 30, 2000 2:31 PM
Subject: Re: Restrict jobs CPU usage


> This seems to be a common misconception among the midrange community.  I
> have run into programmers who describe programs as "dogs" solely because
> they use 100% of the CPU time.  This has nothing to do with whether the
> program is good or not.  It merely reflects that the system is well
> tuned to performing this task and that the Job does not have to wait for
> resources to become available.  The amount of resources that a program
> uses to accomplish a task (CPU, Disk IO etc.) is an entirely different
> matter.
> In the Vax/VMS environment that I used to program in the goal was to get
> as close to 100% CPU Utilization as possible.  Of course at the same
> time you wanted the minimum amount of CPU time to be used.
>
> John Hall
> Home Sales Co.
>
> simon.thompson@distserv.boc.com wrote:
> >
> > Anton,
> >
> > Your analogy might be useful. Performance figures are sent weekly to one
> > of our clients (who actually pay for the boxes and our time). The powers
> > that be, for some reason, think that showing near 100% is embarassing
for
> > us. Personally I would have thought that it showed that we are using
> > their machines quite well.
> >
> > Simon
> +---
> | 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
> +---

+---
| 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
+---


+---
| 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
+---