Apache JMeter Room for Improvement

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. View full review »

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. View full review »

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. View full review »

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. View full review »

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. View full review »

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. View full review »

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. View full review »

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. View full review »

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

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. View full review »

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. View full review »

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. View full review »

The user interface is a little bit tricky. View full review »

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. View full review »

The tool should be made a bit more robust, and better support should be made available. View full review »