Less14 3 e_loadmodule_4
-
Upload
suresh-mishra -
Category
Technology
-
view
823 -
download
0
description
Transcript of Less14 3 e_loadmodule_4
Copyright © 2008, Oracle. All rights reserved.
Reports & Graphs
Introduction to Oracle Application Testing Suite: e-Load
Copyright © 2008, Oracle. All rights reserved.14 - 2
Reports & Graphs
Generates Graphs and Charts to help analyze potential bottlenecks
Allows you to chart historic test data with recently executed test data
Copyright © 2008, Oracle. All rights reserved.14 - 3
Reports & Graphs
Copyright © 2008, Oracle. All rights reserved.14 - 4
Session Report
Session report is an overview of the test
May be exported to a CSV file for portability and distribution of results
Copyright © 2008, Oracle. All rights reserved.14 - 5
Create Graphs
Provides solid data for later use regarding the last test
Provides statistics for Script Execution Times
Provides metrics such as the following:
• Total Virtual Users
• Transactions (Script Executions) per Second
• Pages & Hits per Second
• Total Transactions Executed
Contains last executed Virtual User configuration
Copyright © 2008, Oracle. All rights reserved.14 - 6
Create Graphs
Click on New Graph to generate a new graph
Copyright © 2008, Oracle. All rights reserved.14 - 7
Create Graphs
Filters let you select which Data Series to plot on the graph
Copyright © 2008, Oracle. All rights reserved.14 - 8
Create Graphs
You can save the graph in various formats
Copyright © 2008, Oracle. All rights reserved.14 - 9
Performance vs. Time
Performance vs. Time:
• Gives script completion times during the total test execution.
• This trend should remain flat unless a defect occurs within the web application.
• A bottleneck will cause performance time (script completion times) to increase
• Invalid server responses may cause decreases in performance times.
Copyright © 2008, Oracle. All rights reserved.14 - 10
Performance vs. Time
Copyright © 2008, Oracle. All rights reserved.14 - 11
Errors vs. Time
Errors vs. Time:
• Number of errors encountered at the time of execution
• Should always remain at zero.
• Occasional spikes mean occasional failures.
• Increasing spike frequency over time may indicate that the server cannot withstand the existing load without throwing an error.
Copyright © 2008, Oracle. All rights reserved.14 - 12
Errors vs. Time
Copyright © 2008, Oracle. All rights reserved.14 - 13
Errors vs. Users
Errors vs. Users:
• Same as “Errors vs. Time” except that the graph is plotted over the total number of users run during the test.
Copyright © 2008, Oracle. All rights reserved.14 - 14
Errors vs. Users
Copyright © 2008, Oracle. All rights reserved.14 - 15
Performance vs. Users
Performance vs. Users:
• Shows script completion times given vs. the total active users.
• Graph should remain flat unless a defect occurs within the web application.
• A bottleneck will cause performance time to increase.
• Invalid server responses will cause the performance time to decrease.
Copyright © 2008, Oracle. All rights reserved.14 - 16
Performance vs. Users
Copyright © 2008, Oracle. All rights reserved.14 - 17
Statistics vs. Time
Statistics vs. Time:
• Shows Kilobytes/Second, Transactions/Second, Pages/Second, and Hits/Second.
• As users continue to increase, KB/Sec should increase.
• If KB/Sec remains does not increase given increasing users, there may be a an issue with the application keeping up with the load applied.
• If KB/Sec decreases given increasing users, a bottleneck may exist.
• Heavy KB/Sec fluctuations may indicate unstable servers given the current load.
Copyright © 2008, Oracle. All rights reserved.14 - 18
Statistics vs. Time
Copyright © 2008, Oracle. All rights reserved.14 - 19
Statistics vs. Users
Statistics vs. Users:
• Same as Statistics vs. Time but potted over the actual number of users run during the test.
Copyright © 2008, Oracle. All rights reserved.14 - 20
Statistics vs. Users
Copyright © 2008, Oracle. All rights reserved.14 - 21
Support
http://metalink.oracle.com