在vuser方面，Jmeter vs LoadRunner

问题描述

我发现了相互矛盾的信息，一种说法是JMeter产生的负载比LR能产生的负载大得多，另一种说法则相反.据我所知(如果我们不考虑许可)，每个LoadGenerator仅受硬件限制.但是JMeter也是如此.该文档对我没有太大帮助.有没有人有这两种经验，以便他可以比较?我说的是2000-4000个用户.谢谢

I have found contradicting information, one saying JMeter can produce much more load then LR can, the other saying the opposite. From what I know (if we do not consider licencing), each LoadGenerator is only limited by hardware. But so is JMeter. The documentation did not help me much.Does anyone have an experience with both of these so he can compare? I am speaking about 2 000- 4000 users.Thanks

推荐答案

LoadRunner可以在开箱即用的情况下通过大量测试很好地运行.

LoadRunner is known to run well with very high volume tests, as is, out of the box.

在以下情况下，JMeter通常可以通过高吞吐量，高线程测试来解决问题:

JMeter can typically hit issues with high throughput, high threaded tests in the following scenarios:

1. 使用一台具有大量侦听器的计算机以GUI模式运行-这会占用内存.
2. 在默认配置中使用版本<的分布式模式. 2.9在Load Generator上运行测试没有问题，但存在将结果发送到主计算机的瓶颈.据报道，此问题已在2.9中解决，吞吐量据称在2.10中更高.

问题是，解决JMeter的问题并不难.这只是最佳做法.

The thing is, it's not that hard to solve JMeter's problems. It's simply a matter of best practice.

1. 从命令行运行，不要使用大量的侦听器.精益和均值模式.
2. 在分布式执行中，使用批处理模式来减少版本为< 2.9或使用> = 2.9的默认配置.
3. 确保您在足够的硬件上分发测试.顺便说一下，LoadRunner也是如此.

您应该阅读这两个文档以获得其他最佳实践:

You should read those 2 documents for other best-practices:

• http://www.ubik-ingenierie.com/blog/jmeter_performance_tuning_tips/
• http://jmeter.apache.org/usermanual/best-practices.html

• http://www.ubik-ingenierie.com/blog/jmeter_performance_tuning_tips/
• http://jmeter.apache.org/usermanual/best-practices.html

LoadRunner在高负载下也有问题-分析和数据整理阶段可能要花几个小时(从字面上看)，您无法避免.如果要分析的数据太多，也可能会遇到内存问题. Jmeter在结果分析方面不那么全面，但是速度更快.

LoadRunner also has issues at high load - the Analysis and data collation phases can take hours (literally) and you can't get around this. If you have too much data to analyze you can also run into memory issues. Jmeter is not as comprehensive at results analysis but it is much quicker.

如果您真的需要进行大量测试，那么我写了一个脚本，它可以有效地为您提供JMeter的无限扩展能力-我ve对多达2万名用户进行了测试，使50台服务器上的8000次命中每秒.这是无限的"，因为它通过运行许多相互隔离的测试来工作，这些测试直到测试结束才互相交谈，这样就不会出现编译结果的瓶颈.但是总会有另一个瓶颈...

If you really need high volume tests then I wrote a script that effectively gives you infinite scalability with JMeter - I've tested it up to 20000 users making 8000 hits a second running over 50 servers. It's 'infinite' because it works by running lots of isolated tests that do not talk to each other until the end of the test, that way there is no bottleneck with compiling results. But there's always another bottleneck somewhere...

这篇关于在vuser方面，Jmeter vs LoadRunner的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！