If you were talking to someone whose organization is considering Apache JMeter, what would you say?
How would you rate it and why? Any other tips or advice?
For the load test which requires high transactions per second to be achieved, in the range of 15K transactions per second, this is a very good tool to use and the biggest advantage is that it is free. It has a big user group, so we can find solutions easily if there are any challenges. It's really a very good open-source tool for any organization to look at in terms of performance tests. I would rate this solution an eight out of 10.
If companies have mobile development, they should use JMeter. If they want to integrate it with the PA pipeline, JMeter will work well. However, there are other platforms and solutions as well. Other options include Silk Performer and Load Impact. These two solutions have other capabilities that JMeter doesn't have. You can basically model your load and structure with them. You can't do that on this solution. On Silk Performer, you can also do network packeting, which you can't do on JMeter. Then there are some network features available in Load Impact as well as Silk Performer that aren't in JMeter. I'd rate the solution eight out of ten. The solution has certain limitations, but it's still a good product.
JMeter is a good solution but it requires writing manual scripts and takes longer than BlazeMeter. It takes longer to cover the same number of use cases and is not as user-friendly. I would rate this solution a four out of ten.
This is a good solution but many features would have to be added to use this tool alone. Postman has more features, so JMeter is really only good for performance testing. I would rate this solution a seven out of ten.
I would definitely recommend JMeter. It is a very nice tool. It is easy to use and there are several components already developed in the tool that you can use to simplify the process of defining and redefining scripts. But I would like it to be more flexible and integrate with other tools.
The requirements for most of our customers is to provide them with cheap solutions, and most prefer not to pay for software. This is the right solution for them based on some of the open-source tools that are available. There are some commercial solutions that provide better integration to the solutions that must be tested when running loads. I would rate this solution an eight out ten.
We are using the on-premises deployment model. The advice I would give to others would be to look at your requirements and decide if the solution is right for you. For us, it was API testing and JMeter is very good for this. I'd rate this solution nine out of ten.
For people thinking about implementing the solution, I would advise that they know what protocols they want to work with. I would recommend doing an evaluation of script maintenance. You need to see how stable your automation disk and performance is. I would rate this solution nine out of ten. The solution offers a lot of plug-ins and a huge, continuously developing community that is regularly offering new features and plug-ins.
We are using the private cloud version of the solution. I would rate this solution eight out of ten. If it had a bit of a better user interface, I would rate it higher.