Performance testing checks a system's responsiveness, throughput, reliability, and scalability under workload. It identifies performance issues, confirms requirements, and checks capacity. Key aspects include scalability, stability, availability, serviceability, and speed. Common problems involve memory, code, and hardware/software. Types of performance testing are load testing, stress testing, endurance testing, spike testing, volume testing, and availability testing.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
32 views14 pages
Performance Testing
Performance testing checks a system's responsiveness, throughput, reliability, and scalability under workload. It identifies performance issues, confirms requirements, and checks capacity. Key aspects include scalability, stability, availability, serviceability, and speed. Common problems involve memory, code, and hardware/software. Types of performance testing are load testing, stress testing, endurance testing, spike testing, volume testing, and availability testing.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14
Performance Testing
What is Performance Testing
• Refer to the test activities on checking system performance. It is conducted to determine the responsiveness, throughput, reliability of scalability of a system or application under a given workload. Objectives of Performance Testing • To confirm the validate the specified system performance requirements. • To check the current product capacity to answer the questions from customers and marketing people. • To identify performance issues and performance degradation in a give system. Why Performance Testing • SCALABILITY: will the application handle the expected load and beyond? • STABILITY: Is the application stable under expected and unexpected user load ? • 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 ? What Performance Problems may arise? • Memory Related Problems: i. Application uses more memory than it should ii. Memory Leaks iii. Excessive garbage allocation i.e application create a lot of temporary objects. • Code Related Problems: i. Application Algorithm are not optimal and there are performance bottlenecks. • Hardware/Software Related Problems: i. Hardware you select for your database is not in vendor hardware list • Response Time: i. After a request is sent to an application response time measure how long it take for a response to return back from the application ii. Slow response time equals an unhappy user experience and may also result in the lose of revenue. • Throughput: i. The amount of transaction produced over time during a tests. ii. Its also expressed as the amount of capacity that a website or application can handle. Types of Performance Testing • Load Testing • Stress Testing • Endurance Testing • Spike Testing • Volume Testing • Availability Testing 1) Load Testing • It help us to study the behavior of the application under various loads. The main parameter to focus is response. This study reveals how the application handles concurrent user affectively. • Response Time 2) Stress Testing • It help us to observe stability of the application. The main intention is to identify the breaking point of the server. The main parameter to focus is throughput (how much data is being transferred b/w client and server. • Response time and throughput 3) Endurance Testing • It reveal about memory utilization when you load your test for prolong executions. Say if you execute your test 1 hour to perform load testing. But in endurance testing you execute your test at least for 8 hours with significant load. • Memory 4) Spike Testing • Spike testing is performed by sudden increase/decrease in load and observing the behavior of the application can handle or not under significant changes in the load. • Response Time 5) Volume Testing • It is the performance to identify whether the server can handle more number of high complex queries under significant load. The main intention is to observe how the database acts under various circumstances. • Response time of queries 6) Availability Testing • This test ensure that the applicant is available 24x7x365 days. If you would have noticed any website hosting providers they advertise as 99 % up time. Availability testing help us to determine whether the application is up and running fine without any issues. • Response Time