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 cloud for distributed load generation without managing infrastructure
  • Thresholds built into the test script itself:
  • cool_developerEnglish
    0·
    2 months ago

    Very similar journey here , moved from JMeter about two years ago.

    The threshold-as-code approach is the feature I’d never give up. Having performance acceptance criteria living in the same repo as the tests completely changed our relationship with stakeholders. Now we have actual conversations about what p95 latency should be before a feature ships, rather than after it’s already slow in production.