Performance testing and j meter overview


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Performance testing and j meter overview

  2. 2. Introductionto Performance Testing  Performance testing is the process of determining the speed or effectiveness of a computer, network, software program or device  Before going into the details, we should understand the factors that governs Performance testing:  Throughput  Response Time  Tuning  Benchmarking
  3. 3. Introductionto Performance Testing Throughput: • Capability of a product to handle multiple transactions in a give period. • Throughput represents the number of requests/business transactions processed by the product in a specified time duration. Response Time: • It is equally important to find out how much time each of the transactions took to complete. • Response time is defined as the delay between the point of request and the first response from the product. • The response time increases proportionally to the user load. Benchmarking: • Benchmarks provide a method of comparing the performance of various subsystems across different chip/system architectures • Benchmarking is the process of comparing your system’s performance against a baseline that you have created internally or against an industry standard endorsed by some other organization.
  4. 4. Types of Performance Testing Load testing  Checks the application’s ability to perform under anticipated user loads. The objective is to identify performance bottlenecks before the software application goes live. Stress testing  Involves testing an application under extreme workloads to see how it handles high traffic or data processing .The objective is to identify breaking point of an application. Endurance/Soak testing  Done to make sure the software can handle the expected load over a long period of time. Volume testing  Under Volume Testing large no. of. Data is populated in database and the overall software system’s behavior is monitored. The objective is to check software application’s performance under varying database volumes.
  5. 5. Why Performance Testing?  Scalability: Will the application handle the expected load and beyond?  Stability: Is the application stable under expected and unexpected user loads?  Availability: Is the application available to the end user without any interruption?  Serviceability: Can the system quickly recover from a failure?  Speed: Does the application respond quickly?  Confidence: Are you sure that clients will have a positive experience on go-live day?
  6. 6. Why to use Performance Testing Tool  Performance testing tool is helping us to reduce risks and minimize costs and for measuring web application performance and load stress capacity. These load testing tools will ensure your application performance in peak traffic and extreme stress conditions This is surely a complex testing which involved objectives of testing, cost, resources involved and potential return.  Performance testing tools aim to make it easy to regularly test and check your website’s performance so that you can then carry out remedial action in order to speed up the time it takes to load each page..
  7. 7. What is JMeter?
  8. 8. JMeter Basics How to launch the Jmeter:  {JMeter home dir -> bin-> jmeter.bat for launch the Jmeter How to increase Heap Memory:  {JMeter home dir}/bin/jmeter.bat How to Run the jmeter:  Ctrl + R to run the JMeter scripts  Ctrl + E to clear the previous results
  9. 9. JMeter Basics Identify the category under which the application falls. i.e. FTP, HTTP, LDAP, JDBC  Creating the test plan  Recording the Scripts  Inserting the timers  Running & Saving the tests  Analyzing the results and check for possible bottlenecks
  10. 10. JMeterComponents/ElementsOverview  Thread Group  Stepping Thread Group  Controllers  Throughput Controller  Transaction Controller  IF Controller  Assertions  Response Assertion
  11. 11. JMeterComponents/ElementsOverview  Post-Processor Elements  Regular Expression Extractor  Listeners  Simple Data Writer  View Results Tree  View Results in Table
  12. 12. JMeterComponents/ElementsOverview  Other Elements  CSV Data Set Config  HTTP Cache Manager  HTTP Cookie Manager  User Defined Variable  Random Variable  Test Action