This document provides an overview of performance testing. It discusses why performance testing is important, the performance testing process, and how to analyze results. The key aspects of performance testing covered include choosing tools, designing test environments, setting targets, scripting transactions, executing different test types, monitoring servers and networks, and performing root cause analysis on test results. Effective performance testing requires thorough planning, proper test setup and execution, and in-depth analysis of performance data.

1. PerformanceTesting
Prepared By : Hassan Mohammed

2. Agenda
▪ Why performance testing?
▪ Fundamental of performance testing
▪ Performance testing process
▪ Result analysis
▪ HP Loadrunner

3. Why performance testing?
▪ What is performance?
▪ Performance optimization areas (software-hardware-network)
▪ Performance Measurement
▪ Service oriented (availability – response time)
▪ Efficiency oriented (throughput – utilization )
▪ Performance standard
▪ SLA (network latency – server availability )
▪ Internet benefits
▪ Note:- If an end user perceives bad performance from your web site, their
▪ next click will likely be on your-competition.com.

4. Bad Performance: Why It’s So Common
▪ The IT BusinessValue Curve
▪ PerformanceTesting Maturity
▪ Firefighting
▪ PerformanceValidation (orVerification)
▪ Performance Driven
▪ Lack of PerformanceConsiderations in Application Design
▪ PerformanceTesting Is Left to the Last Minute
▪ How Many Users AreThere?
▪ UnderestimatingYour Popularity
▪ ApplicationTechnology Impact
▪ Not Using AutomatedTestingTools

5. The Fundamentals of Effective
Application
PerformanceTesting
Performance awareness should be built into the application life
cycle as early as possible.

6. Effective performance testing factors
▪ Choosing an appropriate performance testing tool
▪ Designing an appropriate performance test environment
▪ Setting realistic and appropriate performance targets
▪ Making sure your application is stable enough for performance testing
▪ Obtaining a code freeze
▪ Identifying and scripting the business-critical transactions
▪ Providing sufficient test data of high quality
▪ Ensuring accurate performance test design
▪ Identifying the server and network monitoring key Performance Indicators (KPIs)
▪ Allocating enough time to performance test effectively

7. Choosing an appropriate performance testing
tool
▪ Testing tools architecture
▪ Scripting module
▪ Test management module
▪ Load injector(s)
▪ Analysis module
▪ What to Look for in an Automated
PerformanceTestingTool

8. Designing an Appropriate PerformanceTest
Environment
▪ PerformanceTest environment
▪ An exact or very close copy of the live environment. Ideal
▪ A subset of the live environment with fewer servers but specification and tier-deployment matches to that of
the live environment. frequently achievable
▪ A subset of the live environment with fewer servers of lower specification. most common situation
▪ Virtualization
▪ Load Generators
▪ Load balancing
▪ User session limits
▪ Addressing Different Deployment Models
▪ Available bandwidth
▪ Network latency
▪ Load injection from aWAN location
▪ Network simulation

9. Setting Realistic and Appropriate Performance
Targets. (SLA)
▪ Consensus
▪ Key PerformanceTargets
▪ Availability or uptime
▪ Response time
▪ Concurrency, scalability, and throughput
▪ Network utilization
▪ Server utilization

10. Making SureYour Application Is Stable Enough
for PerformanceTesting
▪ Avoid High data presentation
▪ Update Poorly performing SQL
▪ Large numbers of application network round trips
▪ Undetected application errors

11. Obtaining a Code Freeze

12. Identifying and Scripting the Business-Critical
Transactions
▪ Transaction Checklist
▪ Transaction ReplayValidation
▪ Verify single user replay
▪ Verify multiuser replay
▪ What to Measure? (createTransactions )
▪ To Log In or Not to Log In
▪ Peaceful Coexistence

13. Providing SufficientTest Data of High Quality
▪ Input Data
▪ User credentials
▪ Search criteria
▪ Associated documents
▪ Target Data
▪ Sizing
▪ Data rollback
▪ Runtime Data
▪ Data Security

14. Ensuring Accurate PerformanceTest Design
▪ Performance test types
▪ Baseline test
▪ Load test
▪ Stress test
▪ Soak or stability test
▪ Pacing time &Think time
▪ Injection Profile
▪ Big Bang
▪ Ramp-up
▪ Ramp-up (with step)
▪ Ramp up (with step), Ramp down (with step)
▪ Delayed start
▪ Setting the Number ofVirtual Users per script business case

15. Ensuring Accurate PerformanceTest Design. cont.
▪ Deciding on PerformanceTestTypes
▪ Baseline test each transaction
▪ Load test each transaction
▪ Isolation test individual transactions
▪ Load test transaction groups
▪ Isolation test transaction groups
▪ Soak test transaction groups
▪ Stress test transaction groups
▪ Load Injection Point of Presence
▪ Putting It AllTogether

16. Identifying the Server and Network Key
Performance Indicators (KPIs)
▪ Server KPIs
▪ • Processor utilization percentage
▪ • Available memory in bytes
▪ • Processor queue length
▪ • Physical disk: % DiskTime
▪ Network KPIs

17. Allocating EnoughTime to PerformanceTest
Effectively
▪ Lead time to prepare test environment
▪ Lead time to prepare the injection environment
▪ Time to identify and script business transactions
▪ Time to identify and create enough test data
▪ Time to instrument the test environment
▪ Time to prepare and execute performance test runs
▪ Time to deal with any problems identified

18. PerformanceTest Process
-Prof Of Concept (POC)
-From RequirementTo PerformanceTest

19. Prof Of Concept (POC)
▪ Prerequisites
▪ Process
▪ Deliverables

20. From Requirements to PerformanceTest
▪ Activity Duration Guidelines
▪ Step 1: Pre-Engagement Requirements Capture
▪ Step 2:Test Environment Build
▪ Step 3:Transaction Scripting
▪ Step 4: PerformanceTest Build
▪ Step 5: PerformanceTest Execution
▪ Step 6 (Post-Test Phase): Analyze Results, Report, Retest

21. Interpreting Results: Effective
Root-Cause Analysis

22. The Analysis Process
• Real-Time Analysis
• Response-time data for each transaction in the performance test
• You must be able to monitor the injection profile
• You should be able to monitor the state of all load injectors
• You need to monitor data that relates to any server,
• A display of any performance thresholds
• A display of all errors that occur during test execution
• Post-Test Analysis
• All performance related information that was gathered during the test should be available at the test’s conclusion and
may be stored

23. Types of Output from a PerformanceTest
• Statistics Primer
• Mean and median
• Standard deviation and normal distribution
• Nth percentile
• Response-Time Measurement
• Throughput and Capacity
• Monitoring Key Performance Indicators (KPIs)
• Server performance
• Network Performance
• Load Injector Performance