CONTINUOUS PERFORMANCE MANAGEMENT WITH GATLING

Tomasz Bonior

How to understand Continuous Performance Management

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

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

Return

-data

Examples1) Service stopped working 2) Requirements changes3) Architecture changes

Return

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

This is how we did itInvestment 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

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

Gatling DSLexec(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)

Functional tests in Gatling -> Performance tests “for free”

the same tests with different performance strategy

Functional tests in Gatling -> Performance tests “for free”

\/

generate request/response log

\/

push to GitBook -> API documentation up to date