在 vuser 方面的 Jmeter 与 LoadRunner [英] Jmeter vs LoadRunner in terms of vusers
问题描述
我发现了矛盾的信息，一个说 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:
- 使用一台机器，有很多侦听器，在 GUI 模式下运行 - 这会占用内存.
- 在版本
- 的默认配置中使用分布式模式2.9 在 Load Generator 上运行测试没有问题，但将结果发送到 Master 机器时出现瓶颈.据报道，此问题已在 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.
- 从命令行运行，不要使用大量侦听器.精益和平均模式.
- 在分布式执行中，使用批处理模式来减少在版本中写入一个文件的样本量<2.9 或使用 >= 2.9 的默认配置.
- 确保在足够的硬件上分发测试.顺便说一下，这对于 LoadRunner 也是一样的.
您应该阅读这 2 个文档以获得其他最佳实践:
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
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 的无限可扩展性 - 我'已经测试了多达 20000 名用户，每秒点击 8000 次，运行超过 50 台服务器.它是无限的"，因为它通过运行许多孤立的测试来工作，这些测试在测试结束之前不会相互通信，这样编译结果就没有瓶颈.但总有另一个瓶颈在某处...
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 与 LoadRunner的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
