Slides of my talk about Performance Testing and Gatling @ SoftShake 2013

1. Load testing made easy
Pierre DAL-PRA @ eBusiness Information
@pierre_dalpra

2. Load Testing
Gatling

3. Load Testing
Gatling

4. Load testing?
Performance

5. Performance
Why care?
(from business POV)
It’s all ‘bout the money!
Conversion rates
Platform costs

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

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

8. Performance
Why care?
(from dev POV)
Fun!
(happens to be useful too)
Anticipate
Reproduce
Train

9. Performance
WDYM?

10. Performance
means
Fast?
Robust?
Cost effective?

11. Performance
= Requirements

12. Speed is
suggestive
contextualized

13. Traffic & Behaviors
Analytics
Business people

14. Methodology
(tentative)

15. Prerequisite
Proper local perf testing!!!
client + network
app debugging

16. Be scientists
Analyze!!!
Data
Monitor

17. Tooling
• Load injector: Gatling, JMeter,
Locust.io...
• JVM monitoring: JMXtrans, Yammer
Metrics...
• System monitoring: Nagios
• Network monitoring
• Database monitoring
• Dashboard: Graphite, Ganglia
• Webapp mock: H. Gomez's basic perf
webapp

18. Simulate
Behaviors
Situations

19. Capacity test

20. Stress test

21. Endurance test

22. Metrics
min/max? mean?
The good, the bad
and the ugly

24. Metrics
Percentiles FTW!

25. Iterate!!!
Test
Analyze
Fix hotspot

27. Jmeter, The Grinder,
LoadUI, Tsung, Locust,
Load Runner, Rational,
NeoLoad…

28. Issue #1
High Performance

29. 1 user =
1 thread

30. 50 threads on a JVM

31. With 2000 threads

33. Blocking
I/O

34. Threads ?
Waiting…

35. … and sleeping

37. Issue #2
Usability

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

39. Issue #3
Maintainability

40. What is this change about ?

41. Gatling can
change all that !

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

43. Actors

44. NIO

45. Reach new limits

46. From the Play2 Computer-Database sample.
(cf: https://github.com/gatling/computer-database)

47. Scenario
Scala
= code
= DSL

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

49. … or write your own
Scala code…

50. … or use the Recorder

51. •
•
•
•
Maven Plugin
Maven archetype (run in IDE)
Jenkins plugin
Graphite live reporting

53. Coming soon…
•
•
Websockets, JDBC…
Clustering

55. http://gatling-tool.org
http://github.com/excilys/gatling
@GatlingTool