GTech Technology Focus Group organised an event on "Trends and Transformations on Quality Assurance & Quality Control" This presentation was part of that event which explains how to analyse its result using Load Runner
2. AGENDA
Major outages of web applications
Why load test your application?
Performance testing workflow
LoadRunner: Analysis overview
Major tool vendors/Providers
Q&A
5. WHY LOAD TEST YOUR APPLICATION?
Business Architects & Dev End-Users
Prevent failures on “Go-live” Validating design goals Verifying Consistent end-user
experience.
Baseline against competitors Establishing scalability patterns
and verifying capacity
requirements
Validating functional integrity
under load
Reduce cost of hardware &
software
Optimising software & hardware
configuration settings
for maximum throughput
Ensuring increased confidence in
application
Prevents costly failures of mission-critical applications.
Assures performance under real-world conditions.
Locates potential problems prior deploying application in production.
Sizing your IT components.
Reduces infrastructure costs
6. HOW DO WE TEST FOR PERFORMANCE?
Application
User
Internet
Web Server App Server
Database
Firewall
Load Tool
Recorder
Virtual User
Generated by Load
Tool
14. DEMO: LOADRUNNER ANALYSIS
Application: Flight reservation system (Web based)
Business process: Logon, Search flight, book, check itinerary, Logoff
Load testing was done for 70 users; 2-users @ every 3 seconds
Background
SLA specific goal based on ‘Avg transaction response’ times
Analysis: Inputs
Load Criteria User Load Response times
Light Load Between 0 & 20 5-seconds or less
Average Load Between 20 & 49 10-seconds or less
Heavy Load More than 50 15-seconds or less