I think Mike's suggestion is a good one  - this is how I would approach it
in the context of what you have been asked.

Another good tool is Snapshot/400 ( I think) which has some
good graphical monitoring tools - my experience has been that this makes
performance and response issues more understandable for management types.
The figures seem to reflect the real world as well.

Hope this Helps

Evan Harris

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 by 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.