blocks|key|1613063|text|没有达到每秒所期望的请求数量的原因可以是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1613064|线程组中没有足够的线程|ordered-list-item|1613065|由于缺少资源，JMeter无法发送足够快的请求。|1613066|测试中的应用程序响应不够快。|1613067|关于第1点，请注意，常数吞吐量计时器只能暂停线程，以便将JMeter的吞吐量限制在每分钟所需的请求数。|offset|length|style|BOLD|1613068|如果您使用并发线程组，则切换到吞吐量成形定时器更有意义，它可以通过反馈回路连接到并发线程组，这样JMeter就能够启动额外的线程以达到所需的RPS速率。|1613069|您可以使用JMeter插件管理器安装吞吐量整形定时器|1613070|​|1613071|📷|atomic|1613072|1613073|关于第2点:确保您正在跟踪JMeter最佳实践，并在运行JMeter的机器上监视基线OS健康指标，如果缺少CPU或内存，您可能需要考虑分布式测试。|1613074|关于第3点:与第2点相同的方法是使用分析工具来查看应用程序花费最多时间的地方|1613075|entityMap|0|LINK|mutability|MUTABLE|url|https://jmeter-plugins.org/wiki/ThroughputShapingTimer/|1|https://jmeter-plugins.org/wiki/ThroughputShapingTimer/#Schedule-Feedback-Function|2|https://www.blazemeter.com/blog/how-install-jmeter-plugins-manager|3|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/c5ae17c2157b50c619fc36844c938418.png|imageAlt|4|http://jmeter.apache.org/usermanual/best-practices.html|5|http://jmeter.apache.org/usermanual/remote-test.html^0|0|0|0|0|K|2|R|1|0|F|8|0|X|4|1|0|5|B|2|0|0|0|1|3|0|0|D|A|4|1V|5|5|0|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1P|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|1R|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1S|8|@$K|1T|L|1U|M|N]|$K|1V|L|1W|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1X|8|@]|9|@$K|1Y|L|1Z|1|20]|$K|21|L|22|1|23]]|A|$]]|$1|Q|3|R|5|6|7|24|8|@]|9|@$K|25|L|26|1|27]]|A|$]]|$1|S|3|T|5|6|7|28|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|29|8|@]|9|@$K|2A|L|2B|1|2C]]|A|$]]|$1|X|3|T|5|6|7|2D|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2E|8|@]|9|@$K|2F|L|2G|1|2H]|$K|2I|L|2J|1|2K]]|A|$]]|$1|10|3|11|5|6|7|2L|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|15|16|17|A|$18|1B]]|1C|$5|15|16|17|A|$18|1D]]|1E|$5|1F|16|1G|A|$1H|1I|1J|-4]]|1K|$5|15|16|17|A|$18|1L]]|1M|$5|15|16|17|A|$18|1N]]]]

The reasons of not achieving desired number of requests per second could be in:

<ol>
<li>You simply don't have enough threads in thread group</li>
<li>JMeter cannot send requests fast enough due to lack of resources on its side</li>
<li>Application under test cannot respond fast enough</li>
</ol>

With regards to point 1 be aware that Constant Throughput Timer can only pause threads in order to limit JMeter's throughput to the desired number of requests per minute. 

Given you use Concurrency Thread Group it makes more sense to switch to <a href="https://jmeter-plugins.org/wiki/ThroughputShapingTimer/" rel="nofollow noreferrer">Throughput Shaping Timer</a> which can be connected to the Concurrency Thread Group via <a href="https://jmeter-plugins.org/wiki/ThroughputShapingTimer/#Schedule-Feedback-Function" rel="nofollow noreferrer">feedback loop</a> so JMeter will be able to kick off extra threads to achieve the desired RPS rate. 

You can install Throughput Shaping Timer using <a href="https://www.blazemeter.com/blog/how-install-jmeter-plugins-manager" rel="nofollow noreferrer">JMeter Plugins Manager</a> 

<a href="https://i.stack.imgur.com/sf2DH.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/sf2DH.png" alt="JMeter Plugins Manager Throughput Shaping Timer"></a>

With regards to point 2: make sure you're following <a href="http://jmeter.apache.org/usermanual/best-practices.html" rel="nofollow noreferrer">JMeter Best Practices</a> and monitoring baseline OS health metrics on machine where JMeter is running, if there is lack of CPU or RAM you might need to consider <a href="http://jmeter.apache.org/usermanual/remote-test.html" rel="nofollow noreferrer">Distributed Testing</a>

With regards to point 3: the same approach as for point 2 + use profiling tools to see where application spends the most of time

I'm having trouble achieving the desired 'requests per second' using a combination of 'bzm - Concurrency Thread Group' and 'Constant Throughput Timer' in JMeter.

Structure

My test is structured as follows:

Thread Group 1

<ul>
<li>Constant Throughput Timer</li>
<li>HTTP Request</li>
</ul>

Thread Group 2

<ul>
<li>Constant Throughput Timer</li>
<li>HTTP Request</li>
</ul>

Thread Group 3

<ul>
<li>Constant Throughput Timer</li>
<li>HTTP Request</li>
</ul>

Thread Group 4

<ul>
<li>Constant Throughput Timer</li>
<li>HTTP Request</li>
</ul>

Numbers

I am wanting to achieve 160 concurrent users for each of the Thread Groups.

Thread Group 1 I am aiming to make 350 requests per second, the others are aiming for 160 requests per second.

The Thread Groups have 160 as the 'Target Concurrency'.
Constant Throughput Timer has 21000 for Thread Group 1 (350 rps*60 = 21000 per minute).
Constant Throughput Timer has 9600 for the others (160 rps*60= 9600 per minute).

All of them have 'Calculate Throughput based on: this thread only'

I'm currently only getting a throughput of around 80 rps for Thread Groups 2-4 and less than 10 for Thread Group 1.

I've allowed JMeter to use 4GB of RAM and I'm not using all of this during the test. When I remove all Throughput Timers, I can achieve up to 14k rps.

Am I missing something? Is there a better way to achieve my desired throughput?

JMeter - Achieving Desired Requests Per Second

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在JMeter中使用'bzm -并发线程组‘和’常量吞吐量计时器‘的组合来实现所需的’每秒请求‘是有困难的。结构我的测试结构如下：螺纹组1常通定时器HTTP请求螺纹组2常通定时器HTTP请求螺纹组3常通定时器HTTP请求螺纹组4常通定时器HTTP请求数我希望为每个线程组实现160个并发用户。线程组1我的目标是每秒发出350次请求，其他请求的目标是每秒160次请求。线程组有160作为“目标并发”。

问JMeter -每秒实现所需请求
EN

回答 1

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JMeter -每秒实现所需请求EN