Apache JMeter Reviews

We primarily use it for conducting different types of performance testing, such as load testing, spike testing, and endurance testing.

JMeter is basically the art of the entire performance testing process. We generate load on our application using JMeter and then monitor various metrics like CPU with different monitoring tools. It's the essential foundation for our performance testing.

JMeter is doing some good things with upcoming releases, but the main area for improvement is the extensions available. 

Another area of improvement is the reporting part, specifically regarding report generation. 

There are certain things like we can't merge custom metrics into the JMeter reports. We're limited to JMeter metrics, and other server metrics can't be integrated with JMeter dashboard. This forces us to rely on another tool. 

We should be able to add or custom-configure server details directly in JMeter reports.

We have been using it for three years.

I would rate the stability a nine out of ten.  It's generally quite stable, it hardly has crashes or issues.

Scalability is good for my use cases, but to generate a large load, you must go into distribution mode, which is more complex to configure and requires powerful machines. So, while it's fine for my needs, but the scalability wouldn't be a perfect ten. I would rate it a seven out of ten, as there are some limitations for large-scale testing.

I'm the one who uses it most extensively. And the other we have four to five people are using it just for their local testing. It's development testing kind of stuff.  

It's an open-source community. So we can post our queries there. We generally get good responses from the forums. So it's good enough.

I used another tool like HP LoadRunner. And now it's offered by some different companies, ownership-wise, but it was long back. 

I would rate my experience with the initial setup an eight out of ten, where one is difficult, and ten is easy. Even for new users, the installation is straightforward based on the documentation. 

However, customizing and building something extra can be complex. But overall, it's easy enough to download and start working with.

Our main system is on the cloud, so we primarily use JMeter on the cloud. However, some use cases require on-premises deployment, and we use it there as well.

One person is enough for deployment. The deployment won't take much time. It is very fast, typically within five minutes.

We use the open-source version. 

I'll definitely advise that you should at least give it a try. If it serves your initial needs and meets your expectations, you should go for it. 

It's quite an old and up-to-mark tool with a proven track record in the industry, and there's a strong community behind it. So it's definitely worth giving a shot.

Overall, I would rate the solution an eight out of ten. 

My clients are using it for BI reporting dashboards and executing dashboards. It's basically a reporting tool.

There are many features I like in Apache JMeter. First, it's open source, so I like that about the product. And there's a lot of community support for it.

There are some challenges in terms of recognizing the objects in some critical cases. These are object identifiers because Apache JMeter cannot recognize those dynamic objects.

I have been working with Apache JMeter for 12 years. It has been a long time. 

It is a stable solution. I would rate it a nine out of ten. 

It is an evolving product. It is a scalable tool. I would rate it an eight out of ten. We have medium-sized clients.

Most of the time, we get the solution from the open-source community. However, I have never interacted with Apache's customer support. 

The initial setup is very easy. We always use the latest version. It doesn't take much time to deploy the solution. 

It's a matter of hours to run a full test. However, it may take some time if you need to configure a project and create the skill to run it. Debugging can also be time-consuming. To set up an end-to-end process, it may take several days.

One or two people would be enough for the deployment. Someone from the infrastructure team can provide support in case of port issues, connectivity, or technical challenges. 

I have a different technology stack, such as BI tools like Tableau, Microsoft Strategy, and custom data applications. In some cases, I feel that Apache JMeter is not suitable. So, I am looking out for a different tool.

One tool cannot fit into all kinds of applications and business use cases. But by and large, it can cater to many applications. Overall, I would rate the solution a nine out of ten. 

We have multiple use cases. We have APIs integrated for functionality. We're using JMeter for performance testing those APIs.

There are about 80 people working on this project, and about 12 people are using JMeter for performance testing.

Approximately 10% of people are using JMeter in my organization, and some people are using PureLoad, which is a paid tool.

We're using version 4. The solution is deployed on an Azure public cloud.

The reporting features are really good. There's a lot less latency than other solutions. We configure our API script and execute it through JMeter, get a response time over there, and compare that response time with the Azure cloud response time. The latency is low. JMeter is optimized very well. 

Another valuable feature is that we can distribute our load in different formats, like a responsive load. Then, we can distribute our load in a different manner by using plugins.

We decided to use JMeter because it's open source, and it's a very stable product. There are many plugins that are easily available to configure multiple things.

JMeter is lagging when it comes to GUI performance testing because we need to install some third-party plugins for recording the GUI script, and the performance isn't very reliable. I think it should be improved. The API is pretty optimized, but the GUI isn't.

I use JMeter for API and stress testing, and I use a different tool for GUI testing.

It's pretty stable.

My server is capable of processing 60,000 API requests in one minute. I'm putting 1.2 million API requests per minute on my server because I have configured some scaling rules in the Azure environment. After reaching the optimized level of 60,000 requests, it automatically scales out by one load in the Azure cloud. JMeter generates that load with the specific time we have provided in our script and configuration.

I haven't contacted the official JMeter support channel because if I'm facing any issues, I just Google it. I have found a lot of solutions there because it's open source and multiple people can give their feedback and answer queries. 

The reporting is better in PureLoad because it's a licensed project, but it's okay if the entire report is embedded in Excel format.

There are multiple formats, like tree format and CSV format. In CSV format, you can download your reports. By using some formulas in Excel, you can prepare a similar report. There's automation in PureLoad, but it's not really required in my projects.

Setup isn't complicated. I would rate the setup as eight out of ten.

The speed of setup will depend on your internet speed, but deployment usually takes one to two hours to complete. If you've already written the script, you can easily upload those scripts in JMeter and trigger them. It will take one to two hours to set up all the configurations for JMeter.

The solution is open source.

I would rate Apache JMeter as nine out of ten. There are a lot of features. In terms of stress testing and performance testing, it's really good. There are many plugins available that are compatible with JMeter. You can start your load according to your requirement. JMeter isn't very complex to understand. It's user-friendly and the test results are also available in different varieties, including start, view, trees, and tables.

My advice is that you need to understand the requirements for your project and what needs to be done in terms of performance testing. You also need to think about which plugins serve your purpose. If the plugins and reporting are there, then you should definitely work with JMeter. It's a really good tool with no cost.

You can easily find errors and add or drag in the problem. There are also browser plugins, which support multiple tests and protocol services. In my project, I'm testing MQTT services, which is message queuing telemetry transport. The notification service we're using in our application is related to that. I have tested that particular functionality with JMeter as well because of the security protocol.

JMeter is used by a team of four performance engineers. We monitor tasks on the API level, so all of the requests are hitting individually.

JMeter has helped us streamline our applications by identifying multiple bottlenecks in our systems and exercising tasks against APIs.

JMeter is a free tool with a large user population, which comes in handy because we have a vast knowledge base to tap into when needed. It's also easier to hire consultants who know JMeter.

JMeter's reporting is extremely rudimentary. The fundamental reporting mechanisms need to be drastically improved. It doesn't utilize an automatic session management mechanism or methods other tools use like parsing cookies and variables. Everything needs to be done manually. There's no automation.

We've been using JMeter for the past three years.

JMeter never crashed on us. It's highly stable.

JMeter is highly scalable.

There is no technical support for JMeter.

We previously used LoadRunner, but we switched because the organization had an accumulated knowledge of JMeter. Nobody really knew LoadRunner. However, the biggest advantage is that it's free, and we didn't have to invest in acquiring a performance testing solution.

JMeter is simple to install. We did it in-house, and it takes a day or two to deploy it to the cloud. There's no maintenance required. 

We looked at a number of different tools.

I rate JMeter five out of 10. You need knowledgeable employees to work with the tool because it's difficult to learn. There is a steep learning curve, so you shouldn't expect an entry-level engineer to pick up the tool quickly and become proficient. It takes a considerable amount of time.

We use Apache JMeter to test the performance of our platforms and applications.

The most valuable feature of this solution is that it is free. If not for that, we would be using a different tool.

The graphical user interface could be improved.

In this tool, automation in general is almost non-existent. Everything is done manually. I would advise those who put this together to try to simplify it for their end users, such as being able to automate at their desks. Such as manual relations and social management.

Purely on the feature set, it lacks automation, therefore it requires a lot of manual work.

As a performance engineer, I use it almost every day.

I have been using Apache JMeter for two years.

Apache JMeter seems to be stable enough.

In terms of scalability, we haven't pushed it to a large scale yet.

The majority of users are performance engineers, but there are also some developers.

There are four performance engineers and at least three developers who use JMeter on occasion.

We intend to increase usage, but it is already being used exclusively and extensively.

There is no technical support program for Apache JMeter. There is only an online community of people who help one another.

The community is helpful and fairly advanced.

In the past, I used to use various tools, primarily LoadRunner.

When I changed jobs, and the new company only used JMeter because we didn't have a license for LoadRunner, I started working with Apache JMeter.

The initial setup was very easy.

We used it on a desktop computer. It is also used in the cloud. The idea behind using it in the cloud was to spread loads across multiple machines.

We carry out the deployment ourselves.

We have one performance engineering consultant who maintains this solution.

That would not be applicable because it is a free solution.

Licensing costs are rare.

There are operational costs related to using Amazon Cloud, but the tool itself.

I looked into other options, such as Bluehost, SmartBear, Epic, and LoadRunner but Jmeter proved to be sufficient for our needs.

We chose JMeter based on its pricing structure.

My advice is that it requires a fairly consistent amount of initial learning. It is not simple to learn.

I would rate Apache JMeter a three out of ten.

Apache JMeter's key feature is its ability to manage load profiles, gradually increasing requests over time. This was crucial for us as we tested our application, handling unique protocols and increasing load steadily. JMeter helped identify bottlenecks by measuring response times as we increased request flow rates. This data guided us in optimizing our system's performance and scaling hardware when needed. Recently, new tools like Platinum Consultant have emerged, but I haven't explored them thoroughly. My colleagues prefer these newer tools over JMeter.

JMeter helps us track response times between request and response. As we increase our workload, response times also rise, indicating potential bottlenecks. We use JMeter to gauge when we need to upgrade hardware or optimize our application for better performance. It's effective in measuring various request types and their corresponding response times, making it a valuable tool for assessing system performance.

I appreciate JMeter's simplicity and power for performance testing. While I haven't used all its features, the ability to simulate heavy loads from multiple users is quite beneficial. However, in my current configuration, we haven't utilized this specific aspect of JMeter. Compared to other costly tools like Hewlett Packard, JMeter is free and easier to use, although there are newer tools like Gatling that I haven't tried. Overall, JMeter is simple and effective for performance testing.     

Improving JMeter's sync time could be beneficial. For example, compared to a Hewlett Packard tool that required four machines for load generation, JMeter reduced this to possibly just two machines for the same workload.

I've been a junior with a few years of experience using Apache JMeter for load testing. It's a straightforward tool with useful features, although not entirely unique. 

Scalability is near-linear, especially with custom configurations.

Setting up JMeter is straightforward, not complex at all. Deployment time depends on the code you write for JMeter, which is executed efficiently.I've used it on-premises, but it might also work in a cloud configuration

Since it's free, there's no need for extensive support or improvements in pricing.

Overall, I'd give JMeter a solid ten for its simplicity and effectiveness in typical tasks. While the UI could be slightly better, it's not a critical issue. JMeter provides valuable data and insights through its graphs, and its main benefit lies in being free, simple to use, and widely recognized.

We utilize it solely for load testing and performance testing. 

JMeter is user-friendly, and that's a notable advantage of JVTech. It's straightforward and easy to use, unlike some other load testing tools, making it very easy to understand.                

I have been using Apache JMeter for the past 4 to 5 years. 

The last time I used it, there were some APIs that I tested, and they were running well before. We didn't make any changes to them, but when I tried to check them again recently, they didn't go through. It seemed like an issue at the integration level. I'm currently working on getting half an automation, where I'll have separate linear and rest. But that's the situation so far.

I prefer tools that I can easily teach people within twenty minutes, and JMeter falls into that category. It's part of the tools I use to help others learn load testing. While JMeter can be a bit tricky, I find it easy to grasp and teach. It's user-friendly, and I can quickly introduce someone to it. It's a tool that I can easily exchange with others, and I aim to achieve proficiency in it soon because of its simplicity and ease of use.

We are using this for performance testing and some automation. We consolidate the test data in our own systems and then use an API to send this data to JMeter. The software testing team then uses it to perform all the tests they wish to do. Nowadays, we are mainly focused on regression testing and working with that.

It works really well. 

To be honest, the UI could be more user-friendly. As a UX guy, I believe it's quite cold. The solution that I have nowadays is a very traditional one. So, there is room for improvement in the UI of Apache JMeter. 

I have been using Apache JMeter for two years. We have it in-house. It's a solution that my company has been using for a long time.

There are around seven users in my company using this solution. 

In terms of setup, it's quite simple. It has its benefits, but we are already used to it. In terms of experience, it could be nicer, to be honest. Sometimes, I get a little bit lost.

Two people are required for the deployment and maintenance. They can be he managers, tech leads, engineers, or developers.

The users need to pay for licenses.

We are not switching because we have several testing teams, and we sell them to several customers. So the solution sometimes is not ours; it's the customer's, and they provide some licenses because usually, companies like Vodafone have corporate licensing. They can provide licensing without being responsible for it. 

We also have our own solutions, but we are not sometimes responsive before saying I don't want to use this or I don't want to use that. Because we are an outsourcing company, we put people accordingly to the field desired by our customers. So if I need a Selenium expert or an Optimum or TestRail, whatever, I go to the market, and I outsource this to the customer.

Overall, I would rate the solution a seven out of ten. I recommend it because I know a lot of people who use it, and they don't have any complaints.