Dlaczego warto regularnie dbać o wydajność aplikacji od samego początku jej tworzenia. Jak można wykorzystać do tego narzędzie Gatling i jakie daje możliwości?

1. CONTINUOUS PERFORMANCE
MANAGEMENT WITH GATLING
Tomasz Bonior

4. How to understand Continuous Performance Management

5. It’s not trendy It’s not jazzy
It’s not fanky It’s not popular
It’s not new
It’s not easy
but maybe worth to try...

6. Investment
- learn tools
- write tests
- setup CI with performance tests
- monitor reports
- maintain tests

7. Return
-data

8. Examples
1) Service stopped working
2) Requirements changes
3) Architecture changes

9. Return
- continuous performance monitoring
- chance for decisions
- leaks identified with lowest cost

10. This is how we did it
Investment for the Performance Tests
- learn tools
- write tests
- setup CI with performance tests
- monitor reports
- maintain tests
Investment for the Functional Tests
- learn tools
- write tests
- setup CI with functional tests
- monitor reports
- maintain tests

11. Gatling
- open source load testing framework based on Scala, Akka and Netty
- friendly DSL
- ability to record tests
- integrated with Maven and SBT
- robust reports
- high performance
and easy to start, quite new, become popular, trendy, jazzy, funky...

12. Gatling DSL
exec(http("Home")
.get("/"))
.pause(7)
.exec(http("Search")
.get("/computers?f=macbook"))
.pause(2)
.exec(http("Select")
.get("/computers/6"))
.pause(3)
users.inject(rampUsers(10) over (10 seconds)

14. Functional tests in Gatling -> Performance tests “for free”
the same tests with different performance strategy

15. Functional tests in Gatling -> Performance tests “for free”
/
generate request/response log
/
push to GitBook -> API documentation up to date