Performance Test Slideshow R E C E N TPresentation Transcript
Determine the usability/effectiveness of an application under load.
Detect bottlenecks before a new system or upgrade is deployed.
Tune for better performance
The peace of mind that it will work on go-live day
alone justifies the cost of performance testing.
Why do we Performance Test..?
What is Performance Testing?
Performance Testing Determines
… while focusing on
Specifically, it answers:
What happens if…?
Myths of Performance Testing
Performance Testing is done to break the system
Performance Testing only involves creation of scripts and running the scripts
Application Changes cause simple refactoring of performance testing scripts
WHY NOT MANUALLY PERFORMANCE TEST? Manual performance testing can be done by gathering numerous folks together and synchronizing executing the transactions. The drawback is that measuring response time depends on user accuracy. And it is very hard to synchronize the testing AND repeat the tests. And the coordination problem is expanded if you think about including international users.
AUTOMATED PERFORMANCE TESTING Replaces real users with virtual users Generate a consistent, measurable, and repeatable load, managed from a single point of control Efficiently isolates performance bottlenecks User Simulation Controller Web Server Application Server Database Internet / WAN
Performance Test Process “Evaluate System”
This is the most important process because it involves …
predicting actual user experience
accessing any system limitations
defining stakeholder expectations
Performance Test Process “ Draft test scripts/scenario” The scripts will contain transactions which are the most intensive activities performed on the application.
Performance Test Process “Execute Performance Tests” LOAD TESTS are the end to end performance test under anticipated production load. STRESS TESTS determine the load under which a system fails and how it recovers from failure. DURATION TESTS are test with a constant load over a period between 8 and 24 hours to determine if an application’s performance degrades over an extended period of time. BASELINE TESTS is the execution, validation, and debugging of scripts collectively in a test scenario. The results will be used for comparison with future testing results.
Performance Test Process “Entire Process” Response Time Degradation Curve
Performance Test Services Database
Network Web Servers App Servers Java
ERP/CRM Protocols Monitors Diagnostics Operating Systems Databases
iPlanet App Server
Platforms We have the ability to mimic many protocols. Here is a list of the protocols. The Diagnostics tool provides a set of Diagnostics modules that trace, time, and troubleshoot end-user transactions across ALL tiers. And while a testing is executing we will monitor your servers! Web Server Application Server Internet/WAN Load Generator Controller Load Balancer
Performance Test Triggers?
Increasing Number of Users
Operating System Upgrades
Slow application response
Here are some examples of what should trigger a performance test execution!
Performance Test Toolbox Our team has the latest and greatest tools…!!!
Project Team Collaboration
Develop Manual Test Conditions, test data, and expected results
Identify and document business performance requirements
Manages the application implementation
Analyzes and tunes the database
Server System Administrator, Configure downstream and
Closely involved in identifying bottlenecks, tuning
Manage and secure the platform on which applications reside
A successful performance test execution relies on involvement from the entire team..!!
How do you engage our team?
Answer: Just open up a Performance Test SOS ticket…
More information about performance testing is on the