The document discusses load testing using Gatling, emphasizing its importance in assessing application performance during various load conditions. It outlines different types of load tests—capacity, stress, and endurance—while discussing the financial implications of performance metrics. The document also highlights the advantages of using Gatling over other tools by focusing on asynchronous processing and the actor model for better usability and maintainability.

1. Load Testing with Gatling

2. Hat’s off for Stephane Landelle

3. Introduction
Gatling
Demo

4. Load testing?
Checking the performance of your application
under normal and peak load conditions.

5. Types of load tests
● Capacity Test
● Stress Test
● Endurance Test

6. Capacity Test
Goal: Determine how much load your system
can hold

7. Stress Test
Goal: Study system behavior in case of heavy
load, during AND after

8. Endurance Test
Goal: Validate system behavior after a long
period of activity.

9. Performance What for?
(from business POV)
It’s all ‘bout the money!
Conversion rates
Platform costs

10. Results/page : 10 => 30
➔ +500 ms
➔ -20% pages seen

11. +100 ms
➔ -1 % sales
➔ Estimated loss: $160M/y

12. How?
1.Define goals
- Requirements
2.Analyze
- Data
- Monitor
3.Simulate
- Behaviors
- Injector
4.Iterate!!!

14. Load testing tool
Jmeter, The Grinder, LoadUI,
Tsung, Locust, Load Runner,
Rational, NeoLoad…

15. Issue #1 High Performance

16. 1 user = 1 thread

17. 50 Threads on a JVM

18. With 2000 threads

19. Blocking I/O

20. Threads? Waiting…

21. … and
sleeping

22. Can you trust your results ?
JMeter2.8 perftest, expecting 300 tr/sec

23. JMeter reference test with Gatling,
expecting 300 tr/sec

24. Issue #2 Usability

25. Graphical User Interface

26. Issue #3 Maintainability

27. What was this change about?

28. Synchronous - Asynchronous
1user=1 thread - Actor model
Blocking I/O - Non blocking I/O

29. Be asynchronous,
embrace the actor model

30. Use non-blocking I/O
● Async HTTP Client
● Netty

31. Scenario
= Scala code
= DSL

32. Demo

33. Use the rich DSL …
Checks
regex / css/ xpath/ jsonPath
find / findAll/ count
is / in / not / whatever
Structures
doIf/ repeat / during / asLongAs
randomSwitch/ roundRobinSwitch
Error handling
tryMax/ exitBlockOnFail
Feeders
csv/ tsv/ jdbc

34. or write your own Scala code…

35. or use the Recorder

36. References
http://gatling.io
https://github.com/gatling

37. Thank You