Apache JMeter Reviews

We are writing scripts using various tools in multiple environments. We have tests set up where you have to pass the credentials in to get a session ID, and it sets and checks the cookies. Then, we check the response values and pass them on to the next function.

We have this solution integrated with Jenkins and we also use it for database performance testing.

The most valuable features are the integration with Jenkins and the reporting.

JMeter allows us to automate performance testing and raise diagnostic functions.

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.

I have been working with Apache JMeter for the past three months.

We have not had any problems with stability.

So far, I haven't had any issues with scalability when performance testing.

We have not yet been in contact with technical support.

I have also started working with BlazeMeter. One of the differences is that the automation is not possible in BlazeMeter. However, BlazeMeters allows for the selection of different bandwidths, it takes less time to write tests, and it is more user-friendly.

The initial setup is straightforward. We have not yet completed our full deployment with all of the tests.

Our internal team was responsible for the implementation.

We are currently comparing the differences between Apache JMeter and BlazeMeter.

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.

I was experimenting with Apache JMeter. I was doing a proof of concept for myself to see if it fit my needs. I wanted to compare it with LoadRunner to see how it compares in terms of recording, ease of use, and functionality.

I like the fact that JMeter integrates well with other tools. For instance, we are also looking at OctoPerf and, I know for OctoPerf, you can import JMeter scripts, whereas, for LoadRunner, you cannot import LoadRunner scripts into OctoPerf.

I like the graphing; it is good.

Once I got past the learning curve, it was okay.

There were a lot of features that translated well from LoadRunner. I have LoadRunner experience, so once I applied my base knowledge to JMeter, then it was okay. The terminology was a little different, but the functionality is similar. For instance, They are called "extractors," in JMeter and called "correlation" in LoadRunner. 

Once I learned the terminology and how to navigate through JMeter, then it was easier.

I still think LoadRunner is a better tool, but for some purposes, JMeter would suit the need.

The installation needs some work. It could be simplified.

When compared with LoadRunner, LoadRunner is a more mature product.

I used it for a couple of weeks.

It's pretty stable, I don't have any complaints.

We didn't do a large load test. I didn't explore the scalability.

I was the only person using this solution, but I ran 100 user load tests.

I did not need to use technical support.

Previously, we were testing LoadRunner.

I reviewed some YouTube videos and went through them. It wasn't necessarily intuitive.

There was some configuration, and file that had to be set up.

It wasn't like LoadRunner where they have an automatic installer and wizard that does everything for you.

It wasn't as easy, but anyone who is technical can work through it.

When comparing the price with LoadRunner, and if the cost is an issue then JMeter is a better choice. LoadRunner is very expensive.

I like LoadRunner better, although I might be biased because I do have LoadRunner experience. I am a little more familiar with it. I was leaning towards LoadRunner.

I would advise others to look at YouTube videos for the setup. Other than that, it was pretty straightforward. I was pretty much satisfied with it. It's a good tool, and it sounds like it's been around for a while.

I would rate Apache JMeter a seven out of ten.

We primarily use the solution for performance download testing.

It's a solution that's easy to use. It's a bit different from SoapUI and LoadUI.

The user interface is a little bit tricky.

The solution is very stable.

It's not 100% scalable like LoadUI, but LoadUI is very expensive. We're an outsourcing company, so we have approximately ten users. We may have plans to expand in the future.

The solution doesn't have technical support. If we need answers, we look for them on the internet.

Previously, we used the basic version of LoadUI. We switched because LoadUI is very expensive and Apache JMeter is free.

The initial setup was complex. We did have it done in a day. It took approximately one hour. We have about five to six people that manage the solution.

The solution is free. You don't need to worry about licensing costs.

We didn't evaluate other options before choosing this solution.

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.

Almost all features provided by JMeter are helpful.

We have a solution called Service Quality Manager portal and is a web based solution to do service management. We do performance testing of this solution using JMeter. It allows us to simulate a load of concurrent users on our application and find out performance bottlenecks in the application.

Reporting feature can be improved to provide better test results.

We have been using JMeter for 5 years.

I did not encounter any issue while deploying JMeter.

I did not encounter any issue with stability.

Yes, While running with a large number of simulated users, sometimes we got thread exceptions and we restarted our testing simulation.

As such there is no customer service provided by Apache for JMeter. This software is free to use under Apache licensing system.

We tried BadBoy but it lacked features.

Initial setup of JMeter is simple. A user can go ahead and start using it just by following it's documentation.

We implemented JMeter using our own in-house team.

I am not sure yet.

As it is java based software an can run on any platform supporting JVM.

I would suggest to verify one's own business need and evaluate certain parameters first like Feasibility and Reliability of Automation, Ease in maintenance of automated test cases, Time saving in Manual or Automated Testing.

We are using Apache JMeter for profiling and stress testing the application. It is a part of our delivery architecture to stress test the application. It is a part of the build chain. It is not just something that we use internally to verify what we are going to use or going to do.

In terms of a specific use case, we are using Apache JMeter to simulate user engagement. Our software is about customer engagement, and we use JMeter to simulate the customers and engage them on our platform as aggressively as we can.

The features that I appreciate are quite basic. It is easy to ramp up the threads and start calling the application. A lot of connectors can already be found within Apache JMeter, but we are not using the entire set because the integration between the customers and platform is based on HTTP. We are just going to produce lots of HTTP sequences.

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.

I have about two years of experience with JMeter. I started to use it two years ago with a new job.

It, for sure, is stable. Apache JMeter is a consolidated tool that has survived for several years. 

It is mainly used by automation tools. These automation tools are around whenever needed. We have about 70 people, and this is a spot adoption.

I have never tried Apache support.

The initial setup is quite easy because this is just a compressed archive. There is no real installation of the tool. You just need to extract it to integrate with Jenkins Pipelines and automatic tools by using the command-line calls. After you expand the archive, you have to adjust Apache JMeter to its proper configuration, which is not a big issue.

In terms of open-source adoption, it is completely free.

I would recommend this solution. 

I would rate Apache JMeter a ten out of ten. I don't have anything else to compare it with, and I don't know if a competitor can achieve better.