Good suggestion. Or you can use a Timer as a child of the first sampler; Timers are applied before the sampler(s) to which they apply.
A different approach is to use the http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Constant_Throughput_Timer and use BeanShell to change the throughput: http://jakarta.apache.org/jmeter/usermanual/best-practices.html#beanshell_server This does not change the total number of threads, but does allow the load to be varied at will. However this latter approach is probably better for gradually varying loads. S. On 14/08/07, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > Aha, I think I know this.... > > In addition to the 'normal load' thread group, add a second 'surge load' > thread group to the JMX with a short ramp and high number of threads. In > this new thread group, the first sampler is a Java sampler set to sleep > 'x' seconds. After that initial delay has passed, the 'surge' kicks in. > However, if you iterate this thread group, just note the sleep delay > precedes each surge. > > Kind regards, > Sonam Chauhan > -- > Corporate Express Australia Ltd. > Phone: +61-2-93350725, Email: [EMAIL PROTECTED] > > -----Original Message----- > From: James Hill [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 14 August 2007 4:35 PM > To: JMeter Users List > Subject: Simulating a burst of requests > > I think I've seen something like this before, but couldn't track it > down, so here goes... > > I'd like to be able to simulate a sudden spike or burst of requests > against the webserver I'm load testing. At the moment I have two > machines doing it, so midway through a run I'll hit the server from > another machine with a seperate instance of jmeter running on it. Is > there a more elegant way of doing this i.e. after 1000 samples the > load spikes to 100 threads looped 5 times with a very short ramp up, > before returning to "normal" load levels? > > Any help would be appreciated. > > Regards, > James. > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
