https://bz.apache.org/bugzilla/show_bug.cgi?id=63272
Bug ID: 63272
Summary: Constant Throughput Timer performance greatly
decreased when Flow Control Action used
Product: JMeter
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.1.1
Created attachment 36491
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36491&action=edit
Jmeter plan to reproduce issue reported
JMeter version used : 3.1 and 5.0
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)
OS : Ubuntu 18.04.2 LTS & Ubuntu 14.04
Description:
Since JMeter 3.1 I noticed that the Constant Throughput Timer is unable to
control the tests throughput if a Test Action / Flow Control Action is used
after the Constant Throughput Timer declaration.
With a full test tree I noticed a lost of 30 to 50% of the target throughput.
As soon as the Flow Control Action is removed, tests reach desired throughput.
If a Constant Throughput Timer is used after the Flow Control Action
declaration, tests reach desired throughput. But this means I always have to
declare it inside specific modules, which can make it harder to control when we
need a global throughput.
Please check attached JMX.
As it is , it reproduces the bug. (1k RPM instead of 2k RPM)
Disable the FLOW CONTROL simple controller and see how the RPM reach the
desired 2k RPM.
--
You are receiving this mail because:
You are the assignee for the bug.
