We just raised a $30M Series A: Read our story
2019-07-29T10:12:00Z

What needs improvement with Apache JMeter?

54

Please share with the community what you think needs improvement with Apache JMeter.

What are its weaknesses? What would you like to see changed in a future version?

ITCS user
Guest
1920 Answers

author avatar
Top 10Real User

I sometimes found the documentation to be not as explanatory as I would've liked it. In the cases that I can think of, I was looking for a rather hand-holding approach with Step A, B, and C, but then I realized that with a product that is open source like this, you can't do handholding. That is because there are so many different uses and different unique environments and setups for it, but I remember thinking a few times that if they only just said this. If I were going to be Mr. Selfish and say anything I want, I'd say a full feature GUI that lets me drag and drop different modules in line. It could have a simple-to-use GUI.

2021-07-13T19:14:41Z
author avatar
Top 20LeaderboardReal User

This is a difficult question to answer. On one side, JMeter is very flexible and allows for a high amount of customization. On the other, some tasks are common enough that it merits simplifying the process. Authentication for API testing could use improvement. Currently, it is a multi-step process to call, extract, and utilize a bearer token securely for API calls. This process is becoming a common enough task that a "wizard" for creating and consuming popular authentication models is merited.

2021-03-31T14:27:52Z
author avatar
Top 20Consultant

The installation needs some work. It could be simplified. When compared with LoadRunner, LoadRunner is a more mature product.

2021-02-23T02:08:10Z
author avatar
Top 20Real User

They can improve it a little bit in terms of distribution load testing. We struggled with it during the distribution. In terms of reporting, runtime monitoring is not currently included, and it should be included. They can also improve it on the reporting side in terms of the comparison of the reports. They can also focus more on integration with CI/CD. Currently, people are using their own customized tools. It would be nice if Apache can provide some standard tools and procedures for integration with CI/CD tools like DPR. There are some tools, but it would be nice if official standard tools and procedures are available.

2021-02-16T19:09:41Z
author avatar
Top 5LeaderboardReal User

It should start supporting the presentation layer. It currently provides performance testing specifically at the application and API level. It can be extended to the presentation layer, which includes mainly Angular and React frameworks. It should also be easy to use and easy to train people.

2021-01-04T12:16:37Z
author avatar
Top 5LeaderboardReal User

The solution needs to improve reporting. Currently, there is not enough automation involved with the feature. For example, there should be an automatic way of saving reports. I have also found the recording should be improved too. When you are entering a launch in the controller the recording request should be inside it. Lastly, if they could make the technology better in terms of speed, this would help us.

2020-12-23T15:02:00Z
author avatar
Top 20Real User

The user interface could be improved. If they had better UI, it might make it easier to use. You really need a technical team in order to really utilize the product. The scalability could be better, or the process of scaling itself could be a bit more clear.

2020-12-11T23:45:27Z
author avatar
Top 20Real User

Currently, the integration pipeline is implemented by using Jenkins or a similar tool platform. These are continuous integration tools. As far as I know, integration is done by using custom scripts. It would be good if the integration with a continuous integration pipeline, like Jenkins or Hudson, can be done out of the box without using a script.

2020-11-12T00:57:12Z
author avatar
Top 20Real User

The reporting is not very good. When we run with multiple users, it takes a lot of memory. With respect to the recording and playback functionality, the auto-correlation parameterization is not easy and should be improved.

2020-07-23T07:58:41Z
author avatar
Top 5Real User

We have some scenarios for diameter load testing where TPS requirements are very high, 30K or 40K TPS. In the telco area, this is for simulating mobile usage. However, diameter load testing can be difficult in J Meter. The only way to imitate Diameter requests and process the responses of these requests is to implement them in the code of JSR223 samplers. JMeter generally provides synchronous calls. It's something that could maybe be improved in the future, because for achieving that very high kind of TPS, more than 30K, 40K requires a asynchronous solution. It's not a common thing, it's really very specific to the telco domain and a very few projects.

2020-02-12T17:16:00Z
author avatar
Top 20Real User

The GUI could be improved. When we go into GUI mode, there are occasions where it will not sync with our expectations. There are crashes that happen that will stop the solution from performing. It seems we get minor glitches when we go into GUI mode. The data client architecture that we have isn't so great. If we are to consume the data, it won't clear because there is tech running on different agents. When I need to pull the reports from different agents, it's not user-friendly. The reporting can be difficult to handle. It's hard to increase it if you are working on a client's architecture. It's not easy to get the data from one place or to do customizations. There are other solutions that allow users to model their load and structure with them. You can't do that on JMeter. On other solutions, like Silk Performer, you can do network packeting, which you can't do on JMeter. They should add this to the solution as a capability in the future. The support management needs improvement. Support is coming from consultants; you will not be able to get on-premise support from all of their agents in one place. On Silk Performer, for example, they have the capability where you can basically have a summarized report from different agents.

2020-02-09T08:17:48Z
author avatar
Top 10Real User

This solution should support the Ruby programming language for scripting. JMeter should support dynamic throughput so that we can reduce or increase it during the execution of the scripts. For performance testing, we would like to be able to select different bandwidths such as 3G or 4G. The interface could be made more user-friendly.

2020-02-09T08:17:06Z
author avatarit_user77718 (QA Expert at a tech vendor)
Real User

@UdayKumar 1. JMeter supports Ruby given you place JRuby (https://www.jruby.org/) jar into JMeter Classpath
2. Throughput can be changed dynamically during the runtime via Constant Throughput Timer and Beanshell Server combination (https://jmeter.apache.org/user...)
3. JMeter's connection speed can be throttled to simulate different networks speed via httpclient.socket.http.cps property, see https://www.blazemeter.com/blo... article for more details

author avatar
Top 10Real User

When we are testing with too many threads then the solution hangs. JMeter does not support JavaScript. Automation is difficult in JMeter.

2020-02-03T09:10:18Z
author avatar
Top 20Real User

Considering the kinds of tests we are performing here, where we launch several tests at the same time as a batch request, JMeter is not the best tool for the job. Those kinds of things could be done easily with other tools, like k6. It would be simpler that way. JMeter is a very old tool. It has been around for about 15 years. While it has been improved over the last few years, it is a little complicated to run several tests at the same time with different sites. JMeter could be easier. It would be a great improvement if it was easier to integrate with the CI deployments, with tools like Jenkins or CircleCI.

2020-01-12T07:22:00Z
author avatar
Real User

The solution is new to us. I'm not sure if we're using the full capabilities of the solution yet, but from what we have used, we're quite satisfied. In future releases, it would be helpful if there was an integration with ALM Octane.

2019-10-06T16:38:00Z
author avatar
Consultant

They have to find a way to prepare the script or to prepare a detailed analysis. We have to collect all the information on each of the services we have to call. Based on this they have to collect in the phase of preparation for the performance test and then we can run our audit. It is easy to prepare a script to run a performance test. You can't rely on the support. It's something that is not fully working. The scalability of this solution needs some improvement. There is some work to be done with the integration.

2019-10-06T16:38:00Z
author avatar
Real User

The tool should be made a bit more robust, and better support should be made available.

2019-09-18T07:48:00Z
author avatar
MSP

RegEx Extractor needs improvement. It's a headache for many people. The solution could use some sort of educational features to offer tips and hints to help users navigate it better. They should improve the manuals and help files. I've searched the internet for answers over the past year or so, and I haven't come across anything that is helpful. The community help files are pretty good, but their own help files are not. In the next release, it would be helpful to offer more flexible graph handling to be able to combine different metrics into one graph.

2019-07-29T10:12:00Z
author avatar
Real User

The user interface is a little bit tricky.

2019-07-29T10:12:00Z
Learn what your peers think about Apache JMeter. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
542,267 professionals have used our research since 2012.