On 2 July 2010 07:38, Felix Frank <[email protected]> wrote: > On 07/01/2010 08:27 PM, Deepak Shetty wrote: >> Hi >> First When you need to limit the number of requests /per second use a >> constant throughput timer. >> >> The explanation for the behavior you see is >> If you dont have any timers or anything but just a ramp-up of say 1 second >> and say your pixel takes 0.1 seconds then >> Start of test , JMeter will create 1 thread , thenmake a request , get the >> response back in 0.1 seconds and immediate go and make the second request , >> and so on for the first second , then JMeter will created the second >> thread(ramp up of 1 sec) <snip> > > Doesn't the ramp up specify how long Jmeter takes to launch *all* > threads? So, for 100 threads with rampup 1sec, that would be one thread > launched each 10msec, no?
Yes, the ramp-up time is divided by the number of threads to work out the delay between threads. > Cheers > Felix > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
