Mike,

(jt:  You might want to read this, too.)

I really like the format you are using with the various time buckets.  After
running down several dead-end paths,  the only performance file (QAPM*) I see
that has this kind of information is QAPMRESP which is for twinax attached
workstations only.  The Performance Tools Manual shows a report for Locally
Attached Workstations as well as one for Remote Workstations.  I am not finding
this type of info for LAN attached Client Access type workstations.

Is your report showing the Client Access workstations or just the twinax type?

If I understand correctly, Performance Tools presents reports and screens based
on the data that is collected by the QPFRMON job that starts when you run a
STRPFRMON command.  (I am not sure if/how this is related to the CRTPFRDTA job
that is always running in QSYSWRK.)  We don't have Performance Tools, but before
I spend money, I would like to have some assurance PT can actually provide the
info I need.

Phil


   <snip>
   Enough of my stories.  My thought is that you use another metric for
   response time.  This assumes you can get someone to buy into the idea that
   sometimes response time is an application problem or design issue.  I think
   this is real critical.   What we measure is the 'distribution curve of
   response times'.  Everyone is going to be slightly different but what we
   measure is the standard 4 buckets: 0-1 second, 1-2, seconds, 2-4 seconds,
   4+ seconds.  95% of our transactions fall within sub-second, 98% within 2
   seconds, and so on.   Right now I forget how we track that but I am pretty
   sure it is a component of performance tools.
   <end snip>




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.