116 complaints extracted from 116 reviews of Apache JMeter between 2015-05 and 2025-12, average rating 4.26/5, grouped into the problems users report most. Each problem links to the market it belongs to and to startup ideas built on it.
The problems Apache JMeter users report
JMeter too hard to run correctly — 23 complaints about Apache JMeter; 23 complaints across 1 product · market pageUsers consistently hit three walls: setup is manual and fragile (proxy configuration for recording, memory tuning, CLI required for real load), the GUI gives almost no guidance so beginners waste hours on wrong configurations, and results are unreliable or uninterpretable without deep expertise. Specific complaints include threads hanging and requiring forced kills, no built-in reporting, inability to verify JavaScript rendering, and needing to understand workstation bottlenecks just to get trustworthy numbers.
First-time setup and configuration failure — 13 complaints about Apache JMeter; 32 complaints across 4 products · market pageUsers across JMeter, Bigtop, Yetus, and Apidog consistently describe the same wall: initial configuration is opaque, error messages don't guide recovery, and getting to a working state requires hours of trial-and-error or finding scattered tutorials. Complaints range from 'setup is a pain' and 'the master-slave configuration is a little bit confusing' to 'you need to have technical know-how' and 'it's tricky to configure until you work with it a lot and look at examples.' The problem isn't that the tools are bad — it's that the gap between 'installed' and 'actually running a test' is filled with undocumented decisions that punish anyone who hasn't already done it before.
Ugly, confusing UIs blocking non-developer testers — 11 complaints about Apache JMeter; 20 complaints across 3 products · market pageUsers across JMeter, Yetus, and Apidog keep hitting the same wall: the interfaces are functional for engineers who already know what they're doing, but hostile to anyone who doesn't. Complaints range from 'the UI is slightly rough in places' to 'it would be great to have a simple UI for business users' to graphic and import/export bugs that make even basic workflows unreliable. The core frustration is that powerful testing infrastructure is locked behind interfaces that assume you already understand the underlying system.
Testing tools won't connect to CI/CD pipelines — 9 complaints about Apache JMeter; 16 complaints across 3 products · market pageUsers across multiple testing tools describe the same wall: they can't get their test setup wired into a CI/CD pipeline without significant manual work and undocumented workarounds. Complaints range from 'it can be a bit difficult to set it up as part of an automated test system' to 'the integration with my JIRA is still not there' to frustration that connecting to company-specific tooling requires technical knowledge most testers don't have. The gap isn't that integrations are impossible — it's that they require specialists to implement something that should be repeatable and handled once.
Testing tools slow down on large projects — 7 complaints about Apache JMeter; 19 complaints across 3 products · market pageUsers across multiple testing tools consistently hit the same wall: as projects grow — more test cases, bigger request bodies, larger collections, more team members — the tools themselves become the bottleneck. Complaints range from 'UI response speed slows down as project size grows' and 'lags when working on big projects' to 'quite slow if you try to transfer test results from multiple servers in real time.' The problem isn't flaky networks or bad machines — it's the tools loading, syncing, and rendering too much data at once, making the act of testing slower than what's being tested.
In their words
“xml is not a good script format, and hard to reuse or structured in a large project.”1.5/5 · 2015-12-23
“Poor user interface.”2/5 · 2019-09-10
“not much user friendly as it could be and very less documentation”2.5/5 · 2023-01-05
“The scripting doesn't lend itself well to reuse, you can't make modules of functions and call them into other tests.”2.5/5 · 2019-03-01
“It would be better if such plugins get added automatically whenever I select any test element or type.”3/5 · 2022-08-05 · Testing tools won't connect to CI/CD pipelines
“Technical knowledge needed to set it up and make it run automated tests integrating with customer/cd pipeline”3/5 · 2021-11-30 · Testing tools won't connect to CI/CD pipelines