Re: [squid-users] Patching Squid 2.6 icap patch with Squid-2.6.STABLE10 - problem

On Tue, Jan 29, 2008, Amos Jeffries wrote:

> I had Adrian benchmark 3.x recently. With his specific RAM-pathways test.
>
> The cutoff for speed seems to be Squid3 reaching 500-650 req/sec and
> Squid 2.6 going past that into the 800-900 req/sec ranges. At a few
> hundred concurrent requests.

http://squidproxy.wordpress.com/ has the graph if anyone is interested.
Thats on a PIII-Celeron 633mhz box with 128KB of L2 cache.

I've got some munin graphs showing Squid-2.6, Squid-2.7, Squid-2.HEAD and my
hacking branch (s27_adri) which will appear in HEAD as time/funding permits;
I've got s27_adri handling a non-disk workload of ~250 req/sec across a LAN
with about 15% CPU free. Squid-2.6, 2.7 and 3.0 all max out at about 180-200
req/sec on the same test.

Unfortunately its a bit tetchy - if the concurrent client count grows above
about 800 clients, the CPU usage spikes to full, concurrent client count
sits at about 3000 and the service time increases to ~1.5 seconds. Squid-2.X
and 3.X do this straight away. Not much can be done about this besides
making the code more efficient (or buying more hardware, but that peaks out
after a certain point too.)

So if you're running ~100 req/sec, Squid-2.6, 2.7 and 3.0 will be fine for you.
If you're wanting to push things slightly harder (say, >1000 req/sec), come see me.

Adrian
Received on Mon Jan 28 2008 - 21:07:48 MST