Perf Reporting
Perf Reporting
Perf Reporting
Scott Barber
Chief Technology Officer
PerfTestPlus, Inc.
“This chart shows that the home page meets the 6 second
response time requirement 90% of the time under the
tested user load. The requirements demand 95%
compliance. Page1 was the next slowest page, but it
achieved the required response time.”
“The red line shows that the CPU of the web server
bounced between 0 and 100% utilization during a test
run that was not designed to be stressful. This is
abnormal and needs to be researched further.”
www.PerfTestPlus.com Effective Performance Test Reports Page 12
© 2006 PerfTestPlus, Inc. All rights reserved.
Component Performance Chart
Good for:
• Identifying various resource usage.
• Determining issues such as memory leaks.
Not good for:
• Response time reporting.
• Results from multiple tests.
Notes:
• Charts like this one can be created during your script by putting
agents on the servers to be monitored.
• Charts like this one can also be created using tools like Perfmon,
Perfmeter and Top.
“This chart shows that response times for both Home Page
and Page1 degrades dramatically and unacceptably at
200 hourly users and via modem connection speeds.”
www.PerfTestPlus.com Effective Performance Test Reports Page 18
© 2006 PerfTestPlus, Inc. All rights reserved.
Response Time by Test Execution
Good for:
• Comparing specific page response times across multiple tests.
• Graphically displaying scenarios performance side-by-side.
• Highlighting test configurations with universally poor performance.
Not good for:
• Displaying component/resource data.
Notes:
• This chart and table must be created in Excel from data exported
from TestManager.
Scott Barber
Chief Technology Officer
PerfTestPlus, Inc