Load Testing Crash Course with Gatling by Stéphane Landelle

QA had thoroughly tested the new release, performed Unit tests, functional tests and yet... we still crashed.

The ultimate goal in development is to make sure the application works for the end users in the production env, not just in QA.

This is where load testing comes in.

This session will give you some basics about load testing, how to avoid common pitfalls and how to build efficient load tests with Gatling and Java.

We're going to talk about network protocols, application behavior and stats.

STÉPHANE LANDELLE
After a decade of Java consulting, Stéphane has been trying his best to be a good open-source citizens.

He's the founder of the open-source load testing tool Gatling, for which he's also the CTO since it became a company, as well as the maintainer or committer of several other open-source projects, including Netty and scala-maven-plugin.

His main interests are the JVM ecosystem, in particular Scala.

When he's not working or coding, you can find him on a role-playing-game table.

------------------------------------------------------------
INTRO
* visuals & editing by @Mercator
* music : Avocado by Ephixa

[mostinho]

19:30 different types of load tests
Capacity test - keep increasing users/sec arriving to find your breaking point
Stress test (impulse response)
Soak test (high load held for loong time)

24:00 avg and std dev alone are not good measures because even if your avg is low there are many users who will experience higher response times and if distribution of response times isn’t normal then std won’t make sense

Before that, most systems are open model meaning new users are injected into the system as they arrive. Closed systems have fixed number of users in the system at any time (say 50 users and when user is done the test injects a new user to keep at 50)

[kings]

Was a holistic walkthrough of creating and running script with Gatling with a publicly available video game sample application.
🙏 and ❤ from Chennai 🇮🇳

[luizaculau]

Thank you very much for the talk, very clear and concise explanations!