Re: largest deployment?

Hehe, more fun. I just did some log analysis:

cut -d. -f1 access.log | uniq -c | sort -n

And I found out that my numbers were quite off. At the peak rate,
The machine handled 343 requests in 1 second (holy sh*t!). I'm
going to make a graph. Once I've got my 100BaseTX switch, I
can REALLY pound it. (can anyone say 9 PPro 180es with 500
clients each pounding on a poor little PPro 180 machine?)

I'm going to do some more hacks, one of them involving raising the
listen queue to 1024. Another involving doing the 2.0.33 function
mods (I've got it maxed at 1024 because (select?) breaks things).
I've got to compile it with poll instead, and get the hacks so
the machine'll boot. I figure that the absolute maximum upper
limit is 1024 hits per second.

Just sharing some Squid tests! Kickass software! I've gotta try
1.2!!!

--Perry

>
> Dancer <dancer@brisnet.org.au> writes:
>
> > 34GB/server, split across half a dozen drives, sharing by squid (no
> > raid). No problems with the ext2 file-system so far. Bearing up nicely.
> >
> > D
>
> Ah, just edge you out. :) 38 gig, P-II 266, 512meg ram, running
> squid1.2. Handing peak loads of 150 tcp/second, 60 min averages in the
> 50 tcp/second.
>
> Michael.
>
>
>

-- 
Perry Harrington        System Software Engineer    zelur xuniL  ()
http://www.webcom.com  perry.harrington@webcom.com  Think Blue.  /\