On 21/05/07, Juansa Benimeli <[EMAIL PROTECTED]> wrote:
Hi,
I have a problem with jMeter 2.2. I'm trying to overload an apache server on
my local network. I'm using 6 computers as a remote jmeter-server and another
one to get the results
That might have the effect of overloading the client computer and its
network connection....
The test plan looks like:
One thread group with 12 threads with a ramp period of 6000 and loop count of
6000
Simple Controller
Cookie Manager
7 HTTP Request (one of them using HTTP User Parameter Modifier)
Aggregate graph.
Aggregate Graph is very resource intensive.
See
http://jakarta.apache.org/jmeter/usermanual/component_reference.html#listeners
Summary Report would be cheaper.
Jmeter is supposed to send 12 * 6 (computers) * 6000 (iterations) = 288000
requests.
Jmeter stop sendigs requests when it gets 12 000 request with no reason. This
number is aprox because I ran the test many times and I get an interval from
9000 to 15000 requests There are no messages in the log files of each
computer. I kept my test runing the whole night and the day after nothing had
happened.
I can see that requests dont get the apache server and if I send the same
request from one of the remote server in the browser I get response.
If I observe the Aggregate graph I can notice that the rate of sending
request decrease progressively.
First try using Summary Report instead of Aggregate Report, as this is easiest.
If that does not help, then run the test on each node in non-GUI mode,
using CSV output, and then combine the results for further analysis if
required.
Make sure the clocks of all the hosts are reasonably well synchronised.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
