Re: Interactive Response Time

[rob@xxxxxxxxx]

Phil,

How much trouble would it be to recreate this situation on a new 400?  Are
we talking about one file - one program, one library and a few programs?
Because after this weekend we will have one big freaking 840 here...  With
a machine with 2-3590's, 1-4gb cartridge, 1-7208, 1-3580, 1-9348

Really delving into the performance tools is a big start.  Frankly I
haven't handled performance here for years - the VP does that, and he is
quite enamored with Management Central, (and pretty free with the checkbook
on 400 hardware).

It sounds like your boss is open to the idea of an upgrade so changing all
slow programs to batch is probably not the way to go.

Rob Berendt

==================
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    prumschlag@phdinc.c
                    om                        To:     midrange-l@midrange.com
                    Sent by:                  cc:
                    midrange-l-admin@mi       Fax to:
                    drange.com                Subject:     Interactive Response 
Time


                    12/13/2001 11:11 AM
                    Please respond to
                    midrange-l








I have been asked to come up with a plan so that no user will ever have to
wait
more than 30 seconds for an AS/400 interactive response.  The request (from
the
company president) was based on a completely out-of-context observation of
one
user who had to wait 2 minutes for a response to one particular screen on
one
occurrence.  The president's intent is good, he just does not know what he
is
asking for.

Because I don't believe his request can be or should be satisfied as he
worded
it, I am planning to reshape it into an initiative to monitor both average
and
longest response times, set goals (not guarantees) for both, be able to
explain
exceptions, and propose a series of solutions that are most cost effective.
I
will report this to him on a monthly basis.  Sounds pretty noble, huh?

Just for the record, Ops Navigator shows that throughout the day our
average
response time is normally under 2 seconds, and often under 1 second.  We
are
running JDE World on a 730 dual processor.

I am sure there are hundreds of ways to approach this (bigger processor,
more
memory, more disks, better management of file sizes, better scheduling of
batch
jobs, LPAR(?),  separate test box, programming changes, yada, yada, yada.).

Here is my question (finally).  Other than pulling out the Performance
Tuning
manuals, is there a quicker/easier/better way to approach this?  Remember,
my
goal is to develop meaningful performance measures and be able to identify
solutions to performance problems.

Thanks.
Phil


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.