DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I set the Constant Throughput Timer to 1500 and the throughput went up to
2500 when I aborted it. This was not the case in the earlier version where
it hovered around 1500. I will try it again today and email you. BTW it is
a SUPERB tool and you deserver a lot of credit for it.
Mohan DeSouza
Do you have more than one thread going? The Throughput timer
acts on each thread independently. Thus, if you have a constant
throughput timer set to 30, and you have 3 threads, your overall
throughput will be 90 (assuming your server can handle that).
I tried it, and it's working for me.
Hi,
just a extra note in the testplanhtml, about the finctional testmode only
working when outputformat is set to xml, instead of the (now) default csv.
Index: test_plan.html
===
RCS file:
Hi
I tried my experiment again. Constant Throughput Timer is set at
200/minute.
But the throughput climbs to 995/minute before I shut the program down.
The number of samples are around 44000 so the throughput value should have
stabilized.
I have attached the jmx config file.
Hope you can fix this
I have also attached the results jmx file.
MOhan
On Thu, 14 Aug 2003 [EMAIL PROTECTED] wrote:
I don't know what this is about - timers seem to work ok for me. Can you be
more specific? How exactly do they keep on climbing?
-Mike
On 13 Aug 2003 at 21:22, Mohan Desouza wrote:
Hi
I
