我在 LR12.55 中创建了一个 TruClient Web (IE) 协议脚本,当我尝试使用 50 个用户运行脚本时,只有一些会进入运行状态(在 25-37 之间),其余的会永远卡在 init 中。
我尝试更改 Controller -> Options-> Timeout 并将 Init timeout 从默认的 180 更改为 999 但它不能解决问题。任何人都可以评论如何解决这个问题????
我在 LR12.55 中创建了一个 TruClient Web (IE) 协议脚本,当我尝试使用 50 个用户运行脚本时,只有一些会进入运行状态(在 25-37 之间),其余的会永远卡在 init 中。
我尝试更改 Controller -> Options-> Timeout 并将 Init timeout 从默认的 180 更改为 999 但它不能解决问题。任何人都可以评论如何解决这个问题????
TruClient 为每个 vuser(虚拟用户)运行一个真实的浏览器,因此系统资源消耗更高 API 级别的测试。50 个 vuser 对于您的负载生成器机器来说可能太多了。
我建议在运行期间检查 CPU 和内存级别。如果其中任何一个利用率超过 80%,您应该在多台负载生成器机器之间分配负载。
如果资源没有得到充分利用,则应分析故障以确定根本原因。
To further e-Dough's excellent response, you should expect not to execute these virtual users on the same hardware as the controller. You should expect at least three load generators to be involved, two as primary load and one as a control set. This is in addition to the controller.
Your issue does manifest as the classical, "system out of resources" condition. Consider the same best practices for monitoring your load generator health as you would in monitoring your application under test infrastructure. You want to have monitors for your classical finite resource model components ( CPU, DISK, MEMORY and NETWORK) plus additional sub components, such as a breakout of System and Application under CPU, to understand where and how your system is performing. You want to be able to eliminate false negatives on scalability where your load generators are so unhealthy that they are distorting your test results - Virtual users showing the application is slow when in fact the Virtual Users are slow because the machine in use is resource constrained.