Performance Testing

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

2 comments

Comments 1 - 2 of 2 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

3 Favorites

Performance Testing - Presentation Transcript

  1. Performance Testing Load Runner Pune October 2008 Parish Sharma
  2. Contents Day 1
    • Session 1: Planning an Effective Load Test.
    • Session 2: Load Runner Flow and Architecture
    • Session 3: Introduction to Scenarios
    • Session 4: VuGen and Scripting
    06/09/09 Author: Parish Sharma
  3. Session 1 Planning an Effective Load Test 06/09/09 Author: Parish Sharma
  4. Types of Performance Test
    • 1. Performance Test
    • 2. Load Test
    • 3. Stress Test
    • 4. Capacity Test
    06/09/09 Author: Parish Sharma
  5. Performance Test
    • Purpose:
    • To determine or validate speed, scalability, and/or stability.
    06/09/09 Author: Parish Sharma
  6. Load test
    • Purpose:
    • To verify application behavior under normal and peak load conditions.
    06/09/09 Author: Parish Sharma
  7. Stress Test
    • Purpose:
    • To determine or validate an application’s behavior when it is pushed beyond normal or peak load conditions.
    06/09/09 Author: Parish Sharma
  8. Capacity Test
    • Purpose:
    • To determine how many users and/or transactions a given system will support and still meet performance goals.
    06/09/09 Author: Parish Sharma
  9. Need for Load Test
    • User support for a New System.
    • Upgrade/Scale a System
    • To know the Speed and Response of the System
    • To know the behavior at normal and peak loads.
    • To identify where system breaks.
    06/09/09 Author: Parish Sharma
  10. Cont..
    • Most load tests are executed with false intentions, (performance barometer).
    • Understanding the impact of response times for predictable behavioral conditions and scenarios.
    • Understanding the impact of response times for patterns of adoption and growth.
    06/09/09 Author: Parish Sharma
  11. Goals & Objectives
    • Performance Testing Objectives
    • Performance Objectives
    • Performance Targets
    • Performance Thresholds
    • Performance Budgets
    06/09/09 Author: Parish Sharma
  12. Measurable Goals
    • 1. Transaction Response Time
    • 2, Resource Utilization
    • 3. Memory Leaks
    • 4. Deadlocks
    • 5. Throughput
    • 6. Capacity Planning
    • 7. Product Evaluation
    • 8. Acceptance
    06/09/09 Author: Parish Sharma
  13. Information to Start
    • 1. Hardware and Software Details
    • 2. Load to be tested
    • 3. Expected Response Time
    • 4. Suitable time to load test.
    • 5. Critical Business Scenarios.
    • 6. Priority and Flow of scenarios.
    06/09/09 Author: Parish Sharma
  14. END OF SESSION -1 QUESTIONS?? 06/09/09 Author: Parish Sharma
  15. Session 2 Load Runner Flow and Architecture 06/09/09 Author: Parish Sharma
  16. Load Runner Components
    • 1. Virtual User Generator
    • 2. Controller
    • 3. Load Generator Agent
    • 4. Analysis
    06/09/09 Author: Parish Sharma
  17. Plan Test Create Scripts Scenario Creation Scenario Execution Result Analysis Load Testing Flow Performance Tuning
  18. Test Planning
    • 1. Test Planning - Before we run load testing
    • - Setup goals
        • Measure application response time
        • Configuration sizing
        • Capacity planning
        • Regression
        • Reliability
    • - Type of testing
        • Load Testing (System performance testing with SLA target load)
        • Stress Testing (Capacity testing to find out breaking point)
        • Duration Testing (Reliability testing to test the system under load)
  19. Create Scripts
    • 2. Create Scripts
    • - Automate business processes in LoadRunner VUGen (Virtual User Generator):
      • Scripts are C, C++-like code
      • Scripts are different with different protocol/technology
      • LoadRunner has about 50 protocols, including WAP
    • Record user actions
      • Need assistance of SME/Functional Testing group
    • Add programming and test data in the scripts
      • E.g. add correlation to handle dynamic data, e.g. session id
      • Test data may need lot of work from project team
  20. Scenario Creation
    • 3. Create Test Scenario
    • - Build test scenario according to usage information in Business Profile
    • Load Calculation
    • Can use rendezvous point, etc.
    • - Run-Time setting
    • Think time
    • Pacing
    • Browser Emulation: simulate browser cache, new user each iteration
    • Browser version, bandwidth, etc.
  21. Test Execution
    • 4. Execute Load Testing
    • Execute test scenarios with automated test scripts in LoadRunner Controller
    • Isolate top time transactions with low load
    • Overdrive test (120% of full load) to isolate SW & HW limitations
    • - Work with Internal Support Team to monitor the whole system, e.g., web server, DB server, middleware, etc.
  22. Result Analysis
    • 5. Analyze Test Result - Analysis
    • - Collect statistics and graphs from LoadRunner
    • - Report results
      • - Most commonly requested results:
      • Transaction Response time
      • Throughput
      • Hits per sec
      • HTTP response
      • Network Delay
      • *Server Performance
      • - Merge graphs to make it more meaningful
      • Transaction response time under load
      • Response time/Vuser vs CPU utilization
      • Cross scenario graphs
  23. Result Reporting
    • 6. Test Report
    • - Don’t send LoadRunner result and graphs directly
    • - Send summary to the whole team
    • - Report key performance data and back end performance data
    • - Add notes for each test run
    • - Keep test history: for team to compare test runs
  24. Architecture Overview 06/09/09 Author: Parish Sharma
  25. How it Works 06/09/09 Author: Parish Sharma
  26. END OF SESSION -2 QUESTIONS?? 06/09/09 Author: Parish Sharma
  27. Session 3 Introduction to Scenario 06/09/09 Author: Parish Sharma
  28. Elements making a Scenario
    • 1. Business Requirements
    • 2. User Load
    • 3. Ramp Up / Ramp Down
    • 4. Steady Run Time
    • 5. Actions of the Users
    06/09/09 Author: Parish Sharma
  29. Scenario
    • Using LoadRunner, we divide the application performance testing requirements into scenarios.
    • A scenario defines the events that occur during each testing sessions.
    • For example, a scenario defines and controls the number of users to emulate, the actions that they perform and the machines on which they run the emulations.
    06/09/09 Author: Parish Sharma
  30. Types of Scenario
    • 1. Manual
    • 2. Goal Based
    06/09/09 Author: Parish Sharma
  31. Types of Execution
      • 20% of Full Load - flush out transaction problems, effectively debug transaction
      • Full Load - flush out system problems, effectively debug system
      • 120% of Full Load (Overdrive) - provide a margin of error as well as future scalability
    06/09/09 Author: Parish Sharma
  32. END OF SESSION -3 QUESTIONS?? 06/09/09 Author: Parish Sharma
  33. Session 3 VuGen and Scripting 06/09/09 Author: Parish Sharma
  34. Virtual Users
    • Virtual users or Vusers emulate the steps of real users. The steps that Vusers perform are recorded in a Vuser Script.
    06/09/09 Author: Parish Sharma
  35. Virtual User Generator
    • VuGen records Vuser scripts that emulate the steps of real users using the application.
    • VuGen not only records VuGen scripts but also runs them. Running scripts from VuGen is useful for debugging.
    • VuGen records sessions on Windows platforms only. However a recorded Vuser script can run on both Windows and Unix Platforms.
    06/09/09 Author: Parish Sharma
  36. Developing Vuser Script
    • Record a basic script.
    • Enhance/Edit the script.
    • Configure the run time settings.
    • Run the script in Stand Alone mode.
    • Integrate the Vuser script into the test.
    06/09/09 Author: Parish Sharma
  37. Vuser Scripts
    • Each Vuser script has 3 sections:
      • Vuser_init{()
      • Actions() {One or more actions can be there}
      • Vuser_End()
    06/09/09 Author: Parish Sharma
  38. Enhancing the scripts
    • After recording the basic script, it can be enhanced with the following:
      • General Vuser Functions.
      • Protocol specific Vuser Functions
      • Standard ANSI C Functions
      • Inserting Transactions into the script.
      • Sending Messages to the output
      • Handling errors.
      • Parameterization
      • Corelation
    06/09/09 Author: Parish Sharma
  39. Run Time Settings
    • Think Time
    • Run Logic
    • Pacing
    • Log
      • Standard
      • Extended
      • Miscellaneous.
    06/09/09 Author: Parish Sharma
  40. END OF SESSION -4 QUESTIONS?? 06/09/09 Author: Parish Sharma
  41. QUIZ TIME!!!!!!!! 06/09/09 Author: Parish Sharma
  42. Questions?
    • [email_address]
    • [email_address]
    • Tel: (020)2620-7710 (desk)
        • 09922429552 (cell)
    06/09/09 Author: Parish Sharma

+ sharmaparishsharmaparish, 8 months ago

custom

748 views, 3 favs, 0 embeds more stats

Performance Testing Basics

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 748
    • 748 on SlideShare
    • 0 from embeds
  • Comments 2
  • Favorites 3
  • Downloads 2
Most viewed embeds

more

All embeds

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories

Tags