Bug 60236 - ThroughputController does not give same results depending on Timer presence or not
Summary: ThroughputController does not give same results depending on Timer presence o...
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 3.0
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-10 20:47 UTC by Philippe Mouawad
Modified: 2018-10-28 20:57 UTC (History)
1 user (show)


Attachments
Test plan to reproduce (7.98 KB, application/xml)
2016-10-10 20:47 UTC, Philippe Mouawad 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2016-10-10 20:47:10 UTC 
Created attachment 34356 [details]
Test plan to reproduce

Find attached a Test Plan showing a different results depending on wether Constant Timer is enabled or not.

Is this regular ?

Thanks
Comment 1 Philippe Mouawad 2018-10-28 20:57:23 UTC 
The timer presence impacts the Throughput Controllers that are not per user.
So the number of runs of Throughput Controller at 20% will differ wether there is a Timer or not.

If we make the number of executions higher then the results are quite similar in terms of repartition.

So it appears it would not be a bug, but another analysis is welcome.

Thanks
Comment 2 The ASF infrastructure team 2022-09-24 20:38:06 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4137