4. Objectives
Reduce Latency
Scale to maximum number of users
Minimize business downtime
Identify hotspots
Infrastructure Assessment and Recommendations
Performance Tuning
4
6. What should we do?(1 of 2)
Benchmarking-Understanding and analyzing how your application or system
performs.
Load Testing-Apply a load representing a high volume operation and/or a
load over a significant time duration.
Stress Testing-Testing to break the system.
Metrics-Indicative.
Finding how many concurrent users system can accommodate.
6
7. What Should we do?(2 of 2)
Number of page views
Number of business objects : Simultaneous competitions,
transactions testing system
Client Application – creates a load that represents one or more
simulated users
Data Collection – application that collects performance counter data that
will be used for analysis
7
8. How it happens?
Input Output
Functionally Tested Guaranteed Performing
Application Application
Study , Questionnaire , Interview , Demo
& Training to get Knowledge Debug Rejected
Transfer Applications
Plan Setup
Run Test
Identify Perfromance &
Cases Accepted
Critical Goals , scripts Test
Transcations & test
setup
Schedule
& Track
8
9. What Next?
On approval of the Performance Testing proposal:
Need to nail down the methodology to be followed
Define Scope
Test Plan
Environment Set up
Build test script
Execute
Performance Reporting
Disaster Recovery Plans
Code tuning techniques
Plan for demographic switching of server instances
9
