jmeter侦听器每秒点击数和合成图生成的图形不正确 [英] Incorrect graph generate by jmeter listener Hits per Seconds and Composite Graph

问题描述

使用jmeter学习并在读取图形侦听器输出时出现问题

learning using jmeter and getting problem when reading graph listener output

1. 创建具有数字线程8，提升1并永久循环的线程组

1. creating Thread group with number thread 8, ram-up 1 and loop forever

随着时间的推移添加侦听器活动线程，每秒的点击次数，多次的响应时间

adding listener active threads over time, hits per seconds, response times over times

结果: 一种.随时间变化的活动线程中的线程数可获得正确的结果，最多8个线程

result: a. in Active Threads Over Time getting correct result with maximum 8 thread

b.在每秒点击数"中，图表结果确实很奇怪，历史记录/秒数为148

b. in Hits per Second, graph result is really weird, there is 148 number of hist/sec

尝试调试线程并将其更改为1，每秒命中数"仍然会以20次命中/秒的速度生成怪异的图表

trying to debug and change thread to 1, Hits per Second still generate weird graph with 20 hits/sec

知道为什么会这样吗? 我使用的是jmeter 3.0的最新版本

any idea why this happening? i use latest release from jmeter 3.0

推荐答案

正如我已经澄清的

As I had clarified here, jp@gc - Hits per Second, this listener shows the total number of requests sent to the server per second. Per Second is by default - it can be changed in the settings tab.

当您有1个用户时，JMeter每秒发送18-20个请求(一旦用户获得响应，Loop将永远为该用户发送请求).因此，该用户能够在一秒钟内发出19个请求.当您有8位用户时，测试计划会发送大约133个请求.它似乎工作正常，在这里也没什么奇怪的.

When you have 1 user, JMeter sends 18-20 requests / second (Loop forever will keep sending the requests for the user as soon as the user gets the response). So, The user was able to make 19 requests in a second. When you have 8 users, the test plan sends around 133 requests. It seems to work fine and nothing weird here.

当您有8个用户时，JMeter在发送前8个请求(每个线程的第一个请求)时不会有任何问题.但是，仅当收到前一个请求的响应时，才发送每个线程的后续请求. (如果您有任何计时器来模拟用户的思考时间，那么用户将在收到响应后等待发送下一个请求的持续时间.)

When you have 8 users, JMeter would not have any issues in sending the first 8 requests (first request for each thread).But the subsequent requests for each thread will be sent only if the response is received for the previous request. (if you have any timers to simulate user think time,then the user will wait for the duration to send the next request after the response is received).

如果1个用户能够发出19个请求(或服务器每秒处理19个请求)，则8个用户应该能够发送152个请求.但是，当您增加用户负载/增加发送到服务器的请求数时，它的吞吐量(服务器可以处理的请求数/单位时间)也会逐渐增加，如图所示.如果不断增加用户，则在某一时刻，您会看到服务器的吞吐量(命中数/秒)趋于饱和/不会超过此点.因此，可能是这里的服务器以133个请求/秒的速度饱和.因此，我们看不到8个用户的152个请求.要了解此行为，您需要缓慢增加用户(提升).

If 1 user is able to make 19 requests (or server processed 19 requests per second), then 8 users should be able to send 152 requests. But, when you increase the user load/increase the number of requests sent to the server, It's throughput (number of requests the server can process / unit time) will also increase gradually as shown in the picture. If you keep increasing the user, at one point, you would see the server's throughput (number of hits / second) gets saturated / would not increase beyond this point. So, may be, here the server got saturated at 133 requests / second. That is why we could not see 152 requests for 8 users. To understand the behavior, you need to increase user (ramp up) slowly.

在此处查看JMeter上的一些提示

Check here for few tips on JMeter

这篇关于jmeter侦听器每秒点击数和合成图生成的图形不正确的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！