El mar, 13-12-2005 a las 18:19, sebb escribió:
On 13/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
However, is there any way to get threads of different machines execute
diferent requests?
Yes, make sure the data files are have different data in them.
That works fine. Thanks sebb!
El vie, 09-12-2005 a las 18:37, sebb escribió:
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 it and works fine if I execute the test
unfortunately, the only way to have each client machine use a test plan is
to start jmeter on several systems and then have a few people help you click
run at the same time.
in the case where you really need each request to be different, due to
caching, I would recommend turning off the cache to
On 13/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
El vie, 09-12-2005 a las 18:37, sebb escribió:
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
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
On 12/9/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
hi!,
I'm using Jmeter to perform a peak test of my web
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,
for what it's worth, it's nearly impossible to get all 100 requests within
500ms. The reason for this is making the initial connection to your
webserver will have a high initial cost. How many iterations are you using.
if you look at all formal performance test specifications, they all have a
First of all, thanks a lot for your answer peter,
I comment it between lines:
El vie, 09-12-2005 a las 16:00, Peter Lin escribió:
for what it's worth, it's nearly impossible to get all 100 requests within
500ms. The reason for this is making the initial connection to your
webserver will have a
your explanation helps, but here's the thing. Say I want to simulate the /.
effect. If 5K people all hit /. at the same exact nanosecond, all the
connections will still be queued up by the server and the webserver will
process them one at a time. As soon as a server thread/precess starts to
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
I understand what you tell me. I think the problem is a set of things:
1.- The server has to queue all the requests. Although it can have
enough threads to handle all of them, only one thread can be in
execution at a given time.
2.- Jmeter has the same problem when launching all the requests.
3.-
El vie, 09-12-2005 a las 18:10, sebb escribió:
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
On 09/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
El vie, 09-12-2005 a las 18:10, sebb escribió:
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
13 matches
Mail list logo
