n 09/12/05, Iago Toral Quiroga <[EMAIL PROTECTED]> wrote: > El vie, 09-12-2005 a las 15:17, Peter Lin escribió: > > I'm not sure I understand why you have 100 thread groups. > > > > you can put the requests in sequence in 1 threadGroup and increase the > > thread count to 100 with 0 second ramp up. > > peter > > Because the requests must be different. If I do what you say, > all the 100 threads within the threadgroup will send the same > request (the first one in the sequence).
Not necessarily. You can use variables in the requests, and read the variables from a file using CSV Data Set. Each thread will get a different line from the file (unless it wraps round). > I tried using an interleave controller to avoid such problem, but the > interleave controller just deals requests for each thread, so the result > is the same. > Anyway, I've also tried having one thread group and 100 threads within > it sending the same HTTP request, but I still have the performance > problem I commented in my previous email. > > Iago. > > > > > > On 12/9/05, Iago Toral Quiroga <[EMAIL PROTECTED]> wrote: > > > > > > hi!, > > > > > > I'm using Jmeter to perform a peak test of my web server (100 http > > > requests at the same time). To do such, I've created 100 thread groups, > > > each one with one thread that sends a different http request. At the web > > > server I log the time (in milliseconds) at which each request is > > > received. > > > > > > I need these requests to be sent to the web server as close as posible > > > but I noticed they are are logged at the web server in a period of time > > > that varies but is never lesser than 0.8 secs. > > > > > > ¿Shouldn't jmeter be able to send 100 requests in a leesser period of > > > time? ¿Is there any way to boost the launching of these requests? > > > > > > I've also noticed that, if I enable the option to parse HTML in each > > > HTTP request (HTTPSampler.image_parser in jmx file), my web server log > > > tells me that jmeter needs 2 or even more seconds to send all the 100 > > > requests, which leads me to think that some threads start processing its > > > response before all requests have been sent ¿can I change this > > > behaviour? This is a big problem, because this way, Jmeter is limited in > > > its capacity to send the requests as soon as posible to stress the > > > server. > > > > > > My test machine has the following features: > > > CPU: 2.4 GHz > > > RAM: 512 MB > > > OS: Debian Linux. Kernel 2.6.12. > > > > > > Thanks in advance for your help. > > > -- > > > Abel Iago Toral Quiroga > > > Igalia http://www.igalia.com > > > > > > --------------------------------------------------------------------- > > > 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]
