I've now checked the code, and can confirm that the threads are all created at once.
Each thread then waits if necessary before starting to run the test plan itself. S. On 22/02/06, sebb <[EMAIL PROTECTED]> wrote: > But do the threads *start* earlier than expected, or is it just that > the threads are created all at once? > > S. > On 22/02/06, Pavel Gouchtchine <[EMAIL PROTECTED]> wrote: > > Hi All. > > I am using JMeter 2.1.1 on Windows XP. > > > > According JMeter documentation: > > " The ramp-up period tells JMeter how long to take to "ramp-up" to the full > > number of threads chosen. If 10 threads are used, and the ramp-up period is > > 100 seconds, then JMeter will take 100 seconds to get all 10 threads up and > > running. Each thread will start 10 (100/10) seconds after the previous > > thread was begun. If there are 30 threads and a ramp-up period of 120 > > seconds, then each successive thread will be delayed by 4 seconds." > > > > I have started to monitor number of threads using Task Manager and I see > > that all threads starts at once, and ramp-up time doesn't play any role > > here. > > For example, when I have Number of Threads: 1000 and Ramp up time 60 sec, I > > am expecting to get all 1000 threads up and running only in 60 sec. That I > > see is different: all 1000 threads started at once. > > > > Is it something, that I am missing in configuration or it is a problem? > > > > Thank you. > > Pavel Gouchtchine > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
