Switching from JMeter was the right call for us!
About 14 months ago our team (based in PAK, B2C platform, peaks around major shopping events) moved our entire load testing suite from JMeter to k6. Wanted to give an honest retrospective now that we’ve been through two major sales events with the new setup.
Why we left JMeter: Not a knock on JMeter — it’s powerful and battle-tested. But for our team:
- XML-based test scripts were painful to maintain and review in PRs
- The GUI was misleading for distributed load generation
- Correlating JMeter output with our Grafana dashboards required too much glue
What we like about k6 :
- Tests are just JavaScript — version controlled, code-reviewed, readable
- Native Grafana integration (they’re the same company now, and it shows)
k6 cloudfor distributed load generation without managing infrastructure- Thresholds built into the test script itself:
Slightly different perspective — we evaluated k6 and ended up staying on Gatling (based in germany but roots in france, so maybe there’s a bias there 😄).
For our use case — complex, stateful user journeys with a lot of conditional logic — Gatling’s Scala DSL was actually easier to model than JavaScript. The simulation concept maps more naturally to what we’re doing.
That said, k6 is clearly the right call for teams who want fast onboarding and tight Grafana integration. They’re both good tools and the JMeter-or-nothing era is happily over.