Thank you for your quick response. I'll try the "boiling frog" test.
Question: When I alter the config files to adjust for the req/sec rate, I
modified the setting in the "robot" parameter from .4 req/sec (default) to
.14 req/sec. I made this change to both config files on the client box and
the server box. Should I have made any adjustments to the server parameter?
-Tim
-----Original Message-----
From: Alex Rousskov [mailto:rousskov@ircache.net]
Sent: Tuesday, May 02, 2000 6:49 PM
To: Tim Eads
Cc: polygraph@ircache.net
Subject: Re: Proxy test - too many errors...
On Tue, 2 May 2000, Tim Eads wrote:
> The majority of the errors are "connection reset by
> peer" errors.
>
> I have 1000 clients on the client box and 540 servers
> on the server box. I have used request rates of .4
> req/sec and .14 req/sec and still receive errors.
Do you have reasons to believe that your installation of Squid or "oops"
can handle 140 req/sec or even 400 req/sec? Connection reset by peer may
indicate that the proxy (or the OS on the proxy box) is overloaded and
cannot handle the traffic.
> I plan on running the same tests again with fewer
> clients - about 300 or so.
I would suggest creating a "boiling frog" workload with request rate
starting from 10/sec and going up to 300/sec within 2 hours. This may
help you to approximate the request rate your proxies can support.
$0.02,
Alex.
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:12 MDT