Re: Squid 2.0 PATCH 2 and cache dir's filling up.

On Tue, Oct 27, 1998 at 09:45:45AM +0000, John Sloan wrote:
>
> See my comments about it being dog slow while doing this. I'm talking
> about 4 hours or so where the cache response is 4-6 seconds instead of
> about 0.8 seconds. This is not an acceptable degradation of performance
> on a live service.
>
> Besides - my cache index file _IS_ on a separate disk.
>

This is why you have several caches (and it's about the only time the
CPU is every utilised to any degree). To resolve the incredibly slow
performance* of 1.NOVM caches on our old systems (P200MMXs/196M of RAM)
I used the Linux local port redirector. When the load average exceeded
a certain amount (say 1.1) for more than 5 minutes it would turn the
http_port off (established connections would remain in place).

Clients would get a connection refused and as they are using Netscape's
auto config (or using the round robin A record) they'd fail over to the
next in line cache.

When the cache was unloaded again (eg after recovering from a crash) the
load would drop, a cron job would nail back up the http_port for clients
to use again.

However, since our P2/512M systems, reloading is about 10 times faster.
The load checker rarely (months go past) has to take down the http_port.

* normal load was ok, just expiring objects or rebuilding from a crash.

tom@interact.net.au
Received on Tue Oct 27 1998 - 06:08:10 MST