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:
  • pakistani_tester1947OPEnglish
    0·
    2 months ago

    Great question. Honestly it’s still our biggest pain point.

    Current approach:

    • Pre-generate a CSV of test user credentials (10k accounts in our staging environment)
    • k6 reads from the CSV using SharedArray so each VU gets a unique user
    • Product/inventory data is refreshed from a staging snapshot weekly via a script

    It’s not elegant. But it works well enough that our load results are meaningfully realistic. The alternative — fully synthetic data — produces numbers that don’t translate to production at all in our experience.