Apache JMeter Reviews

We engage in performance testing using JMeter based on the client's requirements. We decide the endpoints for JMeter based on the domain and application requirements. The requirements, like 50 users per minute or 500 users per hour, guide our performance testing framework.

JMeter has allowed us to effectively verify that, based on pre-requirements, performance standards are met. Since it's an open-source tool, it also allows us to reduce the expenditure on performance testing tools.

The different listeners in JMeter provide various reports and results. It's very useful for performance and load testing. Its compatibility with external tools, such as the ability to import scripts from Selenium and Azure DevOps, makes it a robust and flexible option.

I would recommend the inclusion of plugins for AI in JMeter. Some features still require a certain knowledge level to use effectively, and making these features more user-friendly would be beneficial.

I have not been a direct team member but have managed a team working on JMeter for almost eleven years. In my nineteen years of experience, I have engaged with performance testing, with JMeter being part of our toolkit.

Stability is not a concern for expert users of JMeter. However, stability can be an issue for beginners.

JMeter is widely used and very scalable, rated between eight and nine in terms of scalability. It can also integrate with cloud solutions like Microsoft Azure.

There are many online blogs, forums, and video tutorials available for JMeter, providing substantial support for both beginner and intermediate levels.

LambdaTest and BrowserStack were part of our working user experience, but not extensively more than that. I initially worked with other performance testing tools like LoadRunner.

The setup for JMeter is very easy. There is no installation required; it is simply a package that needs to be imported and can be set up within half an hour or less, depending on the download speed.

Our clients cover the necessary licensing costs, particularly when using cloud services like Microsoft Azure.

JMeter itself is an open-source tool, so there are no licensing costs associated when running on-premises. Client-covered SaaS licensing, such as with Microsoft Azure, does not involve any costs on our side.

It's important to be very skilled in manual testing concepts before starting with performance testing. Due to JMeter's advanced level of techniques and skill requirements, extensive hands-on experience with real-time projects is needed. It generally takes three to four years of practical experience to master.

I'd rate the solution eight out of ten.

The tool helps us in the capacity assessment planning for our services. It helps us to make sure that the APIs will be able to afford the traffic that we expect to get from these services in the production environment. 

The product helps me get the expected performance from applications or servers and reduces costs. It also enhances the performance of the services and helped them reach their ultimate capacity. 

The tool needs to have a better Graphical User Interface. Many of the solution's features are difficult to understand due to the complex user interface and user experience. The product needs to add plugins. It should also work on the integration with external partners like IDE and API gateways. 

I have been using the solution for more than three to four years. 

The tool is stable. 

The product is scalable. My company has around four to five users for the solution. 

The product's setup is not complex. The tool's installation was very smooth.  It doesn't have any deployment process. You just need to implement a set of packages to get started with the product. 

I would rate the product an eight out of ten. 

The solution is primarily used for load testing.

When someone in our organization wants to test web applications, they use Apache JMeter since they face no hurdles while using the solution. Also, we can even increase the number of users using it.

All the features mentioned under JMeter metrics are available to use. Feature-wise, the solution has everything in it that I want.

Self-healing and page rendering for the end-users are not available in Apache JMeter. Hence, these are the two areas that need to be made available in future releases of the solution.

I have been using Apache JMeter for eight years. Also, I am using the solution's latest version, and any of the solution's versions support all the applications in my organization. Our company is an end-user of the solution.

Stability-wise, I rate the solution a seven out of ten.

There are around 50,000 users in my company using the solution. Also, most of the users are involved in performance testing. Scalability-wise, I rate the solution a seven out of ten.

With Apache JMeter, banking processes may face some scalability issues.

There is no support at all for the solution. Basically, it provides zero support.

The solution's initial setup process was straightforward since one only needs to download Apache JMeter and use it after that. Basically, there is no need to do any installation.

There is no need for any maintenance in the solution since it is an open-source product.

Since it is an open-source product, buying or paying for any license is unnecessary. One just needs to download it to be able to use it.

I would recommend the product to those planning to use it as an open-source product, and there is no need to buy a license. So, it is free of cost application. However, I am not sure about the product from a security perspective. But nowadays, banking people are also using it, but it won't be scalable in a banking environment where a large number of people want to use it. Using the solution, one can only test web applications and not use the tool for page rendering. I rate the overall solution a seven out of ten.

I use the solution for performance testing (Load testing, Volume testing and Endurance testing).

The solution has a friendly user interface and is a very good open-source solution for load testing. It supports both web and mobile network recording via proxy and offers a wide range of protocols. It has strong community support across multiple platforms.

The solution is open-source. 

It is very easy to code and develop the script and it supports web and mobile scripting.

There is a lot of good documentation available. 

The solution is stable. 

The memory utilization in JMeter is poor. Limited in terms of scalability. The system gets hung up for complex scripts and heavy loads which requires improvement.

It needs improvement in analytics and statistics reporting. The reports offer limited information on a load test. I would highly appreciate it if JMeter can provide better reporting capabilities.

I have been using this solution for two years.

It's a stable and reliable product. There are no major bugs or glitches and doesn't crash. 

The solution is scalable. However, it has a lot of memory issues during scale-up. That is the one concern. It's a bit limited in terms of scalability.

I have never contacted Apache customer service for any issues. However, the documentation is readily available online and very useful.

The initial setup is pretty straightforward and easy to implement. It's not overly complex. 

I'd rate it a five out of five in terms of ease of implementation. 

I can do the implementation by myself.

It is an open-source tool.

I'd rate the solution eight out of ten.

I mainly use JMeter to check network capacity.

JMeter's most valuable feature is the RegEx Extractor.

Running JMeter in GUI mode uses a lot of memory, which means we need to switch to a non-GUI mode when using a heavy load. There's also a steep learning curve for how to use regular expressions.

I've been using JMeter for over three months.

I would rate JMeter's stability seven out of ten.

I would rate JMeter's scalability as six out of ten.

The initial setup was very easy and took around five minutes.

I implemented JMeter myself.

JMeter is open source and available free of charge.

I would recommend JMeter to other users as it's easy to use and open source, and overall, I'd rate it eight out of ten.

We are using Apache JMeter for automation and for processing activities of our clients. Additionally, it is used for testing.

The most valuable feature of Apache JMeter is its popularity. It is the best open-source tool with all the features needed.

The reports in Apache JMeter could improve.

I have been using Apache JMeter for approximately one and a half years.

The stability of Apache JMeter is good.

Apache JMeter is scalable.

We have less than five people using this solution in my organization.

There is a lot of support available that is good, such as in forums. However, they do not have a dedicated team that you can contact.

I have not used a solution previously.

Apache JMeter was straightforward to install.

The price of Apache JMeter is good. The selling rate is quite effective and the limited users with a multi-region-related execution.

My advice to others is to go through some basic video processes, which are available on YouTube and Apache JMeter site, it has a lot of documentation that will help you get prepared and used to the tool.

I rate Apache JMeter a seven out of ten.

We use it to measure the performance of the system and for balancing.

We like that Apache JMeter has different features and different plugins and that they are free of charge.

We also like that lots of people use it. So, if we happen to get stuck at some point, then we can search for solutions on Google and find them.

Report generation needs to be improved. It is quite difficult to get to.

We've been using Apache JMeter for two years.

It is quite stable.

It is a scalable solution.

On a scale from one to ten, I would rate Apache JMeter at nine. I would recommend it for medium-sized businesses.

In Micro Focus LoadRunner we can go from the UI and we can configure it. There is no such feature in Apache JMeter. There should be UI-based recording history or logs.

I have been using Apache JMeter for one year.

Apache JMeter is stable.

I have found Apache JMeter to be scalable.

Since Apache JMeter is open source there is no vendor support, you have to use the online communities available.

I have used Micro Focus LoadRunner previously and it is better features than Apache JMeter. However, it is not free.

The initial setup was easy for Apache JMeter.

Apache JMeter is a free open source solution and it is why we are using it.

For those who do not want to spend money on tools then this solution would be a good choice. This is the best solution in the open-source category.

I rate Apache JMeter an eight out of ten.

We are using it for load testing. We test other companies' programs.

We are using it just for load testing. We are using its free version, and it is scalable.

I am not satisfied with this solution. Its UI side is not so easy to use for beginners. It should be easier. 

Modeling a test is difficult. If you don't have much knowledge, you won't be able to do it easily. Testing APIs is also difficult.

For JSON, you can use tools such as JSONBuddy, but they are difficult to get in JMeter. It should be easy to get JSONBuddy from the website. I have to use BlazeMeter only to get JSONBuddy.

It has been about five months.

It is not so stable.

It is scalable.

Their support is fine. There are not many Apache documents, but you can find other documents on the web.

It is not so difficult.

We are using the free version.

I would rate it a seven out of 10.

I implement this solution for my clients.

It is very quick and user-friendly.

If the solution was GUI based, I believe that it would be more versatile.

I have been using this solution anywhere from six to eight years.

The solution is stable, I would definitely recommend it to those who are considering it.

The solution is scalable.

No licensing is required as it is a free, open-source tool.