This document discusses performance testing for the Talentcall.com application. The objectives of performance testing are to reduce latency, scale to maximum users, minimize downtime, identify hotspots, and provide infrastructure recommendations. Performance testing benefits include a reliable, scalable and responsive application. The document outlines the performance testing process, including benchmarking, load testing, stress testing, metrics collection, and testing concurrent users and business transactions. It describes how performance testing identifies critical transactions, establishes goals and test plans, runs test cases, and provides performance reports to optimize the application's performance.

1. www.codelattice.com

2. Talentcall.com Phase 1 – Performance Testing
2

3. Why Performance testing?
Application Performance = Brand Performance
3

4. Objectives
 Reduce Latency
 Scale to maximum number of users
 Minimize business downtime
 Identify hotspots
 Infrastructure Assessment and Recommendations
 Performance Tuning
4

5. Benefits!
Reliable Scalable Responsive
5

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

10. THANK YOU
www.codelattice.com
The contents of this document are proprietary and confidential to Codelattice Consulting and may not be disclosed in whole or in part at any time, to any third
party without the prior written consent of Codelattice Consulting.
© 2012 Codelattice Consulting. All rights reserved. Copyright in the whole and any part of this document belongs to Codelattice Consulting. This work may not
be used, sold, transferred, adapted, abridged, copied or reproduced in whole or in part, in any manner or form, or in any media, without the prior written consent
of Codelattice Consulting.
10