Apache JMeter is quite flexible and it is also well distributed. It is quite flexible compared to Micro Focus LoadRunner.
JMeter is easy to script. There is less of a problem with doing correlations and parameterization.
Apache JMeter is quite flexible and it is also well distributed. It is quite flexible compared to Micro Focus LoadRunner.
JMeter is easy to script. There is less of a problem with doing correlations and parameterization.
It is not something that can be compared with Micro Focus LoadRunner. It gives the facility too easily; you do things through UI. With JMeter, you really do not have any easy UI to work as, like a Micro Focus LoadRunner.
The stability could be a bit better.
Compared to LoadRunner, it hasn't any proper UI. Recording the script is also not flexible in JMeter. In LoadRunner, we have a couple of options, such as URL-based recording and HTML-based recording. In JMeter, it's not like that. JMeter has a recorder, however, it is not easy to use. It is a bit tricky to configure the automatic recording in JMeter.
I've been using the solution for four or five years.
JMeter, stability-wise, is good, however, it is being developed by the community. Therefore, stability is always an open question there.
The solution can scale a bit. It is scalable, however, not like LoadRunner. I have not tested it as such yet. I'm not sure about how fully scalable it is.
I'm also familiar with Micro Focus LoadRunner.
The implementation process is not so easy. It's difficult to configure.
I'd rate the solution a seven out of ten.
I'm an end-user and a customer.
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.
Load testing is something that we used to do on Apache JMeter. We have regular releases every two weeks with varying features and modules. For major releases, where most of the EPS are modified or new features are introduced with new pages, we perform a performance test once every three to four months. We have a fixed schedule for performance testing before the sale, such as Thanksgiving and Black Friday, to ensure stability and performance during the sales period.
It is an open-source tool that is easy to use. It can be easily integrated with multiple tools, including Selenium. The tool also provides a recording and playback feature, along with the ability for modification and parameterization. Since it is an open-source tool, it can be easily integrated with many other tools, such as BlazeMeter, making the integration process very helpful.
The UI of the solution needs to be better. The UI takes up a lot of our bandwidth. So, we always run on the command line. Hence, improving the UI is needed. If it can be more lightweight, the editing can also be made easier.
I have been using Apache JMeter for four to five years.
Apache JMeter is a stable tool. Around 10,000-12,000 users are using the tool. One can increase its usage, but we haven't done so since we will need multiple machines to be connected to a network to generate the load. So, we haven't exceeded its use beyond 10,000 users.
Apache JMeter is a scalable tool.
We haven't used the solution's technical support.
We used other solutions in the past, but they were costly since they require a license, whereas Apache JMeter is free. Hence, we prefer Apace JMeter.
The solution's initial setup process was straightforward since setup can be done by opening a JAR file. It can be deployed in half an hour. Experienced people can deploy it in 15-20 mins, and newer ones may take up to an hour.
Also, we don't deploy on any server. Normally, the tests are on local ones.
For deployment and maintenance, you need knowledge of scripting and APIs. But otherwise, maintenance should be easy. Once you record and have the script ready, until and unless there are modifications to the application, maintaining it should not be much hassle.
The implementation was done in-house.
There is no investment as such. Only the resourcing part is there in the tool.
Apache JMeter is a free tool.
I recommend Apache JMeter to others who want to use it. I rate the overall solution an eight out of ten.
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.
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.
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.
The primary use case for the solution is to test web applications.
The most valuable feature is that the solution is open source.
There are a lot of areas in this solution that can use improvement. The solution is not user-friendly, there is no framework for autocorrelation or parameterization.
I have been using the solution for a little over one year.
The new version of the solution is stable.
The initial setup is straightforward as long as you do not require an advanced setup, which can be difficult. The basic setup takes only one hour.
The solution is open-source.
I give the solution
The only support available for the solution is online because it is open-source and does not come with technical support.
To anyone that is thinking of using the solution, I suggest you familiarize yourself with regular expression.
Apache JMeter is utilized for load testing of applications such as APIs and web services. Various types of load testing can be conducted, including stress tests and load tests. It supports different types of protocols, such as HTTP, HTTPS, SFTP, and others.
The most valuable features of Apache JMeter are user-friendliness, large resource, and the quality of assistance they provide. Additionally, it is easy to integrate with cloud platforms, such as AWS.
Apache JMeter could use improvement in reporting. Currently, it isn't easy to generate reports in PDF format. While receiving reports in PDF format is possible, it requires a lot of customization. Additionally, when comparing the load test to others solutions it could improve.
I have been using Apache JMeter for approximately five years.
Apache JMeter is a stable solution.
We have more than 100 people using Apache JMeter in my organization.
We have multiple clients using this solution and all of our testers are using the solution.
My advice to others is for them to go through online tutorials before using the solution. It is easy to use, and anyone can quickly learn and test their application.
I rate the scalability of Apache JMeter an eight out of ten.
I have not contacted technical support.
The initial setup of Apache JMeter is easy and simple to configure. The whole process of implementation takes approximately half an hour. The first step is to download Java and install it. The last step is to download Apache JMeter and install it.
The main reason we chose Apache JMeter is that it is cost-effective and easy to use. There is no need to pay for additional services. Additionally, it does not require additional payment to vendors. The solution is open-source and free.
I rate Apache JMeter a nine out of ten.