DO NOT REPLY [Bug 29708] - startup delay by JMeterThread initialization

[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=29708>.
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=29708

startup delay by JMeterThread initialization

takeichim@nttdata.co.jp changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|startup delay by            |startup delay by
                   |JMeterThread initialization |JMeterThread initialization



------- Additional Comments From takeichim@nttdata.co.jp  2004-06-21 10:29 -------
I'll propose a solution for this issue.

This will enable all the JMeterThread to start at the same time as possible.
As a result, rampup timings will become more accurate.

My proposal consists of the following changes
 1) A JMeterThread waits for the other JMeterThreads in ThreadGroup 
    to be ready.
 2) And then ,the JMeterThreads are notified all together.

Attachments are patch files for this solution.

This function becomes effective when 'sync_threads' property is 'true'
in jmeter.properties.
sync_threads=true

[Note]
 This function cannot support a synchronization of JMeterThreads 
 in different ThreadGroups.

Please let me hear your comments.

Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org