I'm on the squid-dev list. I test and run 1.2-beta caches on a
test-bench server, mimicing the sorts of requests that we get on our
production machines. Too unstable for our needs. We would lose face and
testicles. Big time.
> We run a VERY busy cache, and rarely see over 1500 FDs in use. Unless
> your external links are slower than a wet piece of string (driving up
> your request time-to-complete to the ridiculous), more than 3000fds in
> use is an indicator of a problem elsewhere.
We're hanging directly off the Brisbane Telstra POP (several metres from
the router). Yes, I would say that - at times - a piece of wet string
would be preferable. We hit our problems during upstream network chokes
that officially "don't happen".
> I strongly suspect your squid is bogged down on disk requests causing
> the number of requests outstanding grow to silly amounts. Moving to
> squid 1.2beta22 will dramatically improve your diskk thruput and
> corresponsibly reduce the average request time-to-complete.
No, we don't have disk-choking problems. The disk throughput is still
way short of maxed out.
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GAT d- s++: a C++++$ UL++++B+++S+++C++H++U++V+++$ P+++$ L+++ E- W+++(--)$ N++ w++$>--- t+ 5++ X+() R+ tv b++++ DI+++ e- h-@ ------END GEEK CODE BLOCK------- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu