Découvrez pourquoi (ben oui, au fait, pourquoi?) et comment stresser votre serveur: enregistrer un scenario, jouer avec le DSL, envoyer la purée et interpréter les résultats.

1. Faites tomber la foudre
Stéphane Landelle
CTO
eBusiness Information
@slandelle

2. Yet Another Stress Tool
JMeter, Grinder, Tsung, LoadUI,
LoadRunner, Neoload…

3. Issue #1
High Performance
http://www.shopfbparts.com/catalog/nal-19201331_w.jpg

4. 1 user = 1 thread

5. With 50 threads on a JVM

6. With 2000 threads on a JVM

7. Blocking I/O

8. Threads? Waiting…

9. … and sleeping

10. Is that a real problem?

11. Can you trust your results?
JMeter 2.8 perf test, expecting 300 tr/sec

12. Issue #2
Usability

13. Graphical User Interface
Listen, it's not that
complicated...

14. Issue #3
Maintainability

15. What was this change about?

16. Gatling can
change all
that!
http://static.lexpress.fr/medias/15/mai-68_124.jpg, copyright by AFP

17. Say hello to my little friend…
Version 1.3.5
Released November 2012

18. Be asynchronous, embrace the
actor model

19. Use non-blocking I/O
• Async HTTP Client
• Netty

20. Scenario
= Code (Scala)
= DSL

21. Easy

22. 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

23. … or write your own Scala code…

24. …or use the Recorder

25. Integrations
• Maven Plugin
• Maven archetype (run in IDE)
• Graphite live reporting

26. Coming soon…
• Jenkins Plugin
• Requests Grouping
• Websockets, JDBC…
• Clustering

27. Demo

28. Really efficient?
Jmeter perf test run with Gatling,
expecting 300 tr/sec

29. http://gatling-tool.org
https://github.com/excilys/gatling
@GatlingTool
https://github.com/slandelle
@slandelle

30. Q&A