Bug 64091 - Precise Throughput Timer might produce less samples when low test duration is used
Summary: Precise Throughput Timer might produce less samples when low test duration is...
Status: RESOLVED FIXED
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.2.1
Hardware: PC All
: P2 normal (vote)
Target Milestone: JMETER_5.3.0
Assignee: JMeter issues mailing list
URL:
Keywords: FixedInTrunk
Depends on:
Blocks:
 
Reported: 2020-01-23 08:50 UTC by Vladimir Sitnikov
Modified: 2020-02-15 11:23 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Sitnikov 2020-01-23 08:50:28 UTC
Precise Throughput Timer does not really know how long the test would last.
However, it needs to produce the exact number of samples for the test duration.

That is solved by adding "test duration" parameter to PTT.
If the test lasts longer than the specified duration, then PTT re-generates a next schedule.

However, the glue between those schedules was not right, so the overall schedule might have less samples than desired.

The updated implementation should ensure that each "test duration" timeframe receives exactly the desired sample count
Comment 2 The ASF infrastructure team 2022-09-24 20:38:18 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5227