Re: Measure CPW used

Sue,

The OP was asking if the a 100 CPW machine was running at 50% CPU
utilization, does that mean he's only using 50 CPW?

Or for example, if I've got a 1000 CPW machine I run at 80% usage, so
I'm using 800CPW and I upgrade to a 8000 CPW machine, can I expect to
see CPU usage at 10%?

I realize that these are very simplistic, and the the various workload
tools are going to provide the best answer for the OP, but I think the
OP is trying to get his head around what "then system 2 literally has
twice the computing capability of system1." means to the user.

In fact in your post, you say "if system1 is 1000 CPW and system2 is
2000 CPW, and neither system has bottlenecks in memory, disk, etc. "
Reading between the lines, then the only bottle neck is the CPU in
which case CPW used == CPU% used correct?

Charles Wilt

On Mon, Apr 27, 2009 at 2:38 PM, Sue Baker <smbaker@xxxxxxxxxxxx> wrote:

 wrote on Mon, 27 Apr 2009 17:16:04 GMT:

iNav / Management Central/ Monitors has something called
"transaction rate" but I can't figure if they relate to CPW.

Rob, transaction rate is interactive transactions .... the number
of times someone at a 5250 "device" hits a key that causes the
5250 "device" to go input inhibited and use CPU/memory.

This could relate to CPW, but only for your interactive CPW
feature on older hardware.

CPW is simply a relative performance measurement to make it
easier to compare 2 different systems.  Just like rPerf is used
for AIX workload.

If system1 is 1000 CPW and system2 is 2000 CPW, and neither
system has bottlenecks in memory, disk, etc. then system 2
literally has twice the computing capability of system1.  CPW
tells nothing about the CPU utilization.

--
Sue
Americas Technical Sales Support - Power Systems i
Rochester, MN
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.