You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2006/01/12 12:08:55 UTC
DO NOT REPLY [Bug 38237] New: - Constant throughput timer not working as described
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38237>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38237
Summary: Constant throughput timer not working as described
Product: JMeter
Version: 2.1.1
Platform: Other
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: tkellerer@mgm-edv.de
When I use a constant throughput timer, it seems to be applied to the whole
threadgroup rather then "Only samples within the container where you put the
timer count towards the calculated throughput" as described in the manual.
I have the following test plan
ThreadGroup
+ HTTP Sampler 1
+ Constant Throughput Timer (600/min)
+ HTTP Sampler 2
+ Constant Throughput Timer (60/min)
Both timers are set to "This thread only"
The backend servers are able to handle a lot more than the throughput defined in
the timers (somewhere around 15000/min). But the aggregate report shows the same
throughput for both HTTP Samplers (approx. 3/sec)
Is the manual incorrect, is there an issue with the timer, or am I
misunderstanding something?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38237] - Constant throughput timer not working as described
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38237>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38237
sebb@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From sebb@apache.org 2006-01-12 13:49 -------
Each thread runs Sampler 1 and then Sampler 2, so both timers are applied to
each thread, thus throughput runs at the minimum of the two.
It's not possible for two parts of the same thread to have different
thoughputs ...
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org