DO NOT REPLY [Bug 26007] New: - Ramp Up Time does not work when using Scheduler

[bu...@apache.org]

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=26007>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26007

Ramp Up Time does not work when using Scheduler

           Summary: Ramp Up Time does not work when using Scheduler
           Product: JMeter
           Version: 1.9.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: w.fukushima@pfu.fujitsu.com


In org.apache.jmeter.threads.JMeterThread#run():

            rampUpDelay();
            
            if (scheduler)
            {
                //set the scheduler to start
                startScheduler();
            }


This means that a thread waits ramp up delay then wait until the scheduled time
comes. Now a schedule can be set for ThreadGroup so that all threads in a thread
group start to emit a request in same time, i.e. ramp up time does not work
correctly. Actually first I realized that JMeter acts like that by looking
statistics when testing, then looked for JMeter source codes.

Since we can set a schedule for not an each Thread but a ThreadGroup,
ThreadGroup  should control a delay stems from the schedule. 

Additionally, I wish to set a scheduler with relative time from start. So far
every time I want to (re)start the test, I have to modify each start/end time in
each ThreadGroup... I have to make a tool to shift times in jmx to achieve
that.(sigh)

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