Squid going unresponsive

I've been running Squid 2.2stable4 for a while on a Sun Ultra 5 with Solaris
2.6 for a while without any major problems. I had been running with both
the cache and log files on the same physical disk. 2 days ago, I installed
some new disks and pointed the log files there. The next day I had to
restart Squid 5 times. Everything would work fine for a while and then
response time would go through the roof. cachemgr would show dns lookups,
user authentication, and download times increasing exponentially.
Eventually cachemgr would become unresponsive, and then I would get warnings
in cache.log that Squid was out of file descriptors. I am assuming that
adding the new disk for log files eliminated disk contention as the
bottleneck and that I am now hitting the wall elsewhere. The question I
have is where? It doesn't look to me like I am having memory problems, but
I might add more just to be sure. What happens when Squid is CPU bound?
Does this behavior sound familiar to anyone?

Thanks
Mike
Received on Sat Oct 30 1999 - 16:48:18 MDT