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

It's pretty stable.

Apache JMeter seems to be stable enough.

JMeter, stability-wise, is good, however, it is being developed by the community. Therefore, stability is always an open question there.

The solution has been stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

Apache JMeter isn't as stable because it sometimes crashes when you're running a test. The performance of Apache JMeter could be improved because testing on it isn't always as smooth sailing.

The tool is partially stable. You can't expect Apache JMeter to run well for enterprise-level, high-load applications. It's a good tool for more straightforward or lightweight web applications but not for CRM-type applications.

In terms of stability, there have been some instances of unknown bugs, but these are documented on the official pages and tracked in bug repositories where users can find descriptions and potential workarounds. Users with less experience may encounter unexpected behavior, but with online resources, such as Google, they can understand and address the issues. Some known problems, like internal loop issues when launching from the MacOS terminal, can affect stability, but they are not critical and usually have workarounds. While these issues may slightly impact the user experience, they do not significantly detract from it. On a scale of ten, the overall user experience with JMeter might be rated around seven or eight.

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

I rate the solution's stability as a seven or eight.

It's not stable. With every new release, they come up with newer features, which aren't always very stable. So, stability is a concern.

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.

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

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.

The new version of the solution is stable.

Apache JMeter is a stable solution.

The stability of this product is good, outside of the issues with adding virtual users during testing.

It's hard to say definitively. When there's something wrong with JMeter, we're unsure whether it's something in the device because there are lots of requests coming from the machine. Maybe we didn't use it that many times from our local server. There are some bottlenecks, but in many cases, we only need to restart JMeter, and it works fine.

JMeter can't be used in the long run, so I'd rate its stability as five out of ten.

I rate Apache JMeter's stability a ten out of ten.

The solution is relatively stable. There are no bugs or glitches, and it doesn’t crash o freeze. It’s reliable.

With an on-premises deployment, we run into some performance problems when we have a high load. It's not that stable if we increase the scripts or the load. But that could be something in our environment.

I didn't have any issues with the stability of JMeter itself. There were definitely issues with the program I was testing, but that's why I was testing it.

If you want stability, you will have trouble, because the system is not uniform. You have to do a lot of modeling. 

If you're talking about mobile platforms, JMeter will not allow you to capture the performance of applications on your mobile platform. It's an area where the solution is lacking. It doesn't have the capability to allow developers to check the performance on an AP app.

The stability is good and I am not finding any issues.

It is a stable, reliable product. There are no bugs or glitched. It doesn't crash or freeze.

Apache JMeter is stable, and I personally have not encountered any issues. Depending on the size of test runs, one might need to adjust their JAVA settings to align with the test requirements.

As an open-source tool, when changes happen, it may be a bit unstable. This is occasional, and for the most part, it is fine. I'd rate it seven out of ten in terms of stability. 

The solution is stable. There are no bugs or glitches, and it doesn't crash or freeze.

I am absolutely satisfied with the stability of Apache JMeter.

I rate Apache JMeter ten out of ten for stability.

The solution is stable, and we have not had any issues.

We have found this solution to be a stable and reliable tool.

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

The solution runs on Java software. 

The solution is used to test the stability of other applications through a three-step process. 

Load tests look at the CPU, memory, and APM tool and assess the current load to determine if it can be increased from 60% to 70% for example. You continuously monitor the APM to see fluctuations in memory and CPU usage. If load tests are successful, then you move on to stress tests. 

Stress tests find bottlenecks and determine how many users the application can handle within the current infrastructure. Baseline tests can be performed to determine results such as response time when increasing users. 

Endurance tests determine if an application is stable and for how long stability can be expected. For an endurance test, you set up a particular user load and run it for at least eight hours but up to twenty-four hours. During this time, you see how the application is behaving and whether the CPU and memory are stable. This will allow you to assess overall stability without OOM leakages. 

The solution determines if there are lags in application performance. For one project with 500 continuous users per hour, we used the solution to find that there were only two lags from 50,000 samples generated.  

The solution is stable and easily scalable. 

Apache JMeter is a stable product overall. A very large community in the software industry uses Apache JMeter, and though it's open source and there's a continuous phase of improvement going on with it, it has stable versions available for my company to continue testing it.

This is a stable solution. 

After an update in the application, the stability gets hampered if we continue to use its non-updated version, causing the solution to crash. So, once I faced that problem since I was not updating the application, it crashed. Back then, I wasn't aware that an update was available for the solution, which I had to apply to the solution. So, for two or three days, I tried to solve the issue with the solution. Later, I found that I just needed to update the application. So, after I updated the application, it started working fine. I rate the solution's stability a seven out of ten.

There are issues with stability when running with multiple users because it consumes a lot of memory.

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

It's a well-trusted product. A lot of people use it. There's a lot of support in the community also. Therefore, the stability is pretty good and it is quite reliable.

The stability is quite good. There haven't been any issues with bugs or glitches. It doesn't crash of freeze. It's very reliable.

The tool is stable. 

The stability of Apache JMeter is good.

The stability is pretty good. You can execute any kind of tech with JMeter as well. It's an open-source community. There are a number of samples are available. You can achieve it in different ways, however, the stability is quite good. That said, we have experienced glitches. 

We have found this solution to be very stable overall.

JMeter is probably good for lower loads. It is not comparable to LoadRunner when it comes to higher loads.

It is stable. There is good support, and fixes are also available immediately.

quitre stable but keep an eye on RAM consumption and smart execution tips (can see on their site)

It is stable.

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

Stability becomes an issue if we use more than 10 or 20 threads.

It is quite stable.

We haven't encountered any major issues with the stability.

Apache JMeter is stable.

It is a very stable tool.

The solution is stable.

There are issues when tests are stopped with large number of concurrent users. Test is not stopped as expected.

The solution is stable.

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

This solution is stable, but it does have one limitation with the number of throughputs. For example, if I want to generate four, five, or two thousand people working concurrently then they have to prepare our setup for ten PC servers.

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

See above Room for Improvement.

It is not so stable.

We have not had any problems with stability.

The solution is very stable.

I did not encounter any issue with stability.

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

When I compared this solution to others there were variations in the response times but it is stable.