apache / apache/jmeter

JMeter Response Time Mismatch : Parent Controller Response Time > Sum of Child Samplers Response Time

Open
#5,314 1 comment 0 reactions 0 assignees View on GitHub
os: All P2
Dominant language
Java
Stars
9.5k
Forks
2.3k
Avg merge
1d 22h
Merged PRs (30d)
5

Description

**Deepambika** ([Bug 64444](https://bz.apache.org/bugzilla//show_bug.cgi?id=64444&redirect=false)):
Hi All,

Recently I have observed one issue in JMeter response time population after analyzing the jtl result files of multiple test runs.

Please refer the test settings which I have tried & their observations so far,

Response Time Mismatch - Issue:

Last executed parent controller's response time is greater than the sum of its child samplers response time. Additional response time is not within the think time range. So not sure, from where it's getting that time and adding in parent controller

Response Time Mismatch Occurs (for the below combinations):

Test Duration + Timer (Uniform Random Timer/Constant Timer) + RampDown Time (Example: 1 Hour duration + 20 secs think time + 15 mins ramp down)
Test Duration + Timer (Uniform Random Timer/Constant Timer) + RampDown Time

No Response Time Mismatch (for the below combinations):

Test Duration + No Timer + Ramp Down
Test Duration + No Timer + No Ramp Down
No Test Duration + No Timer + No Ramp Down
Tried JMeter Versions: JMeter 4.0, JMeter 5.0, JMeter 5.1.1

Tried in the latest JMeter version as well - JMeter 5.2.1, but there I have observed 1 more issue where JMeter gives 0 as minimum response time for the last executed parent controller. Will post this issue separately.

Due to security reasons, I am not able to publish or attach my results here as I had this issue in my real time projects.

I have not enabled adding times of the timer in parent controllers.

Thank You

Severity: major
OS: All

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.