Performance testing aims to evaluate how well a system performs under stress by measuring response times, throughput, and resource usage. It identifies potential performance issues by subjecting the system to different types of workload simulations like load, stress, spike and soak testing. Key metrics measured include response times, hits/sec, CPU/memory utilization, and network latency. An effective performance testing approach involves defining goals, requirements, test scripts, monitoring of clients, servers and network during testing, and analysis of results against benchmarks to fine-tune the application.

1. Performance Testing with Gatling!!

2. What is performance Testing?

3. Performance Testing:
In software engineering, performance testing is in general, a
testing practice performed to determine how a system
performs in terms of responsiveness and stability under a
particular workload. It can also serve to investigate, measure,
validate or verify other quality attributes of the system, such
as scalability, reliability and resource usage.

4. Before we talk about performance!!!
Why do we need it?

9. Why Performance Testing?
Performance Testing aims to address 3 key risks :
● Speed - How fast the application responds to a user request!
● Stability - How performant the application is under extended and extreme
conditions!
● Scalability - Is the application future-ready!

10. Performance Testing Types:
● Load testing
● Stress testing
● Soak testing
● Spike testing
● Configuration testing
● Internet testing

11. Load testing

12. Stress testing

13. Soak testing

14. Spike testing

15. Configuration testing

16. Internet testing

17. Client - Server Model

18. Key Metrics to measure the risks
● Response Time
● Throughput
● hits/sec
● Network Latency
● CPU Utilization
● Memory Utilization
● Disk usage

19. Monitor..
● Client
● Server
● Network
● Load balancers (if any)

20. Performance Testing Monitoring:
● CPU Utilization
● Memory Utilization
● Disk utilization
● Network utilization

21. Let’s build a Performance Test Approach
● Evaluate the system and identify the user journeys and critical paths
● Identify the performance goals
● Define the performance testing requirements
● Provision the test environment
● Prepare the test data and test scripts
● Execute the test scripts for various test conditions
● Analyze the execution result and compare against benchmark if any
● Fine-tune the application based on the test observations

22. Example to Performance set goals
1. No response time will exceed X seconds.
2. The average response time will not exceed X seconds.
3. 95% of transactions will take less than X seconds.

23. Workload Modelling
Little’s Law for Performance Testing : N = Throughput * Response Time