Bug 34739 - Enhance Constant throughput timer
Summary: Enhance Constant throughput timer
Status: RESOLVED FIXED
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.0.3
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-04 15:04 UTC by Iulian Cutui
Modified: 2005-05-28 14:53 UTC (History)
0 users


Attachments
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 Iulian Cutui 2005-05-04 15:04:00 UTC 
If you have more than one thread group with a constant througput timer in each
of them set in non legacy mode, then the actual throughput of each thread group
is false computed. The computations are made using
JMeterContextService.getNumberOfThreads(), but this method returns the total
number of threads from all thread groups. The computations should be made using
the number of threads from the current thread group.
Comment 1 Sebb 2005-05-28 14:17:49 UTC 
There are (at least) 3 possible ways of calculating the throughput:
- separately for each Thread (legacy mode = true)
- over all active threads (legacy mode = false)
- over all active threads in the thread group (not yet implemented - but I'm
working on it..)

Seems to me that they are all equally valid.

Changing to an enhancement.
Comment 2 Sebb 2005-05-28 22:53:13 UTC 
Added to CVS HEAD, along with fix for time calculation per thread
Comment 3 The ASF infrastructure team 2022-09-24 20:37:35 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1537