If you don’t know the project, you can look at this article.
From then to now
It’s been almost one year since the first public release of Gatling was announced. What a journey! Here are some numbers about the project:
- 1 major release
- 3 minor releases
- 14 fix packs
- 20k LoC
- 21 contributors
- More than 2500 downloads
- 650 downloads of Gatling 1.2.5 (available two months for download during summer)
- 2 conferences (Devoxx France 2012 and Mix-IT 2012)
- 5 presentations at user groups
Even though I can not contribute to Gatling as much as I have done in the first months, I’m really happy to see the interest in Gatling growing like that :).
Since 1.1, here are the major changes that happened:
- Incremental compilation of scenarios — When executing Gatling you won’t have to wait for all the scenarios to compile each time
- Console Dashboard — More information are displayed in the console when simulations are running
- Real-time feedback with Graphite Integration — Gatling can send data to a graphite server during the simulation.
- Refactored structures — Keeping the DSL simple and explicit is really important, scenarios are even more easy to read/write now
- Many new keywords — There are less and less things that cannot be expressed with the DSL
- DSL for durations — Coming from Akka, durations can be expressed as easily as
- Better performance — Netty has been upgraded, it comes with better performance
- Simple cache support — Gatling will now interpret some cache headers
- Multi file upload — Send many files in your requests
- Redesign of charts for better reading — Gatling’s reports were nice, but now they’re even nicer
- More information for global report — All the details computed for each request are now also computed at a global level
- CSV export of reports — For those who need to work with the data
These are some of the many new features of Gatling. As you can see, there have been many improvements since the first version of the project last year.
Gatling’s lead (Stéphane Landelle) really drives the project toward good quality. To achieve excellent quality, user feedback is very important for us. If you use Gatling and find yourself frustrated about something, you can check the documentation of the project, or its new cheat sheet. If you can’t find an answer to your problem, please start or contribute to a topic on our mailing list :)
For the future, there are at least three other cool features planned:
- A Jenkins Plugin — It already works, but as the code is not ‘good enough’ yet, it should be released in the next weeks
- Request Grouping — It will allow one to create groups of requests to obtain statistics about them in the reports
- Clustering mode — As soon as Akka is realeased with clustering support, we’ll start to work on this
Gatling has also been invited to several user groups in Europe: Luxembourg, Lausanne, Lille, Bordeaux, and others!
If you need a stress tool, give Gatling a try, it’s really worth it! And please, if you find it useful, spread the word :)
EDIT: Added Bastien Lemale to the credits