无法增加jmeter中的平均吞吐量 [英] unable to increase average throughput in jmeter

查看:1026
本文介绍了无法增加jmeter中的平均吞吐量的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我将线程数和加速时间设置为1/1,并且正在从data.csv中迭代1000条记录,持续1800秒. 现在给定数字,我将CTT(恒定时间吞吐量)设置为每分钟2000,我期望平均吞吐量为2000/60 = 33.3/sec,但是当我将吞吐量提高到4000/60时我得到了18.7/sec. ,我仍然可以每秒18或19.

I have set the number of threads and ramp-up time to 1/1 and I am iterating my 1000 records from data.csv for 1800 seconds. Now given the numbers, I have set the CTT, constant time throughput to 2000 every minute and I expected the average throughput to be 2000/60 = 33.3/sec, but I get 18.7/sec, when I increased the throughput to 4000/60, I still get 18 or 19/sec.

推荐答案

恒定吞吐量计时器无法强制线程执行得更快,它只能暂停线程以限制 JMeter的吞吐量到定义的值.

Constant Throughput Timer cannot force threads to execute faster, it can only pause threads to limit JMeter's throughput to the defined value.

每个JMeter线程都尽可能快地执行采样器,但是下一次迭代要等到前一次迭代完成后才能开始,因此如果您使用1个线程-吞吐量不会高于应用程序响应时间.

Each JMeter thread executes samplers as fast as it can, however next iteration won't start until previous is finished so given you use 1 thread - the throughput won't be higher than application response time.

还请注意,恒定吞吐量计时器在分钟级别上足够准确,因此,如果您的测试时间少于1分钟,则您可以操作每分钟的请求数"而不是每秒的请求数"-考虑使用吞吐量整形计时器

Also be aware that Constant Throughput Timer is accurate enough on minute level so you can rather manipulate "requests per minute" rather than "requests per second", if your test is shorter than 1 minute - consider using Throughput Shaping Timer

因此,我建议将虚拟用户数增加到50.

So I would recommend increasing the number of virtual users to i.e. 50.

请参见如何使用JMeter的恒定吞吐量计时器有关更多详细信息.

See How to use JMeter's Constant Throughput Timer for more details.

这篇关于无法增加jmeter中的平均吞吐量的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆