On 09.05.2012 10:03, Henri Wahl wrote:
> Hi
>> What did you run before upgrading?
>>
> 3.1.19.
> Later I compared 2 proxies, one with 3.2.0.17 and one with 3.1.19,
> both
> CARP-clustered OpenBSD 5.1 machines. When we had less traffic over
> night
> and I switched to the 3.1.19 proxy the squid process took like 5%
> CPU.
> When I switched to the 3.2.0.17 proxy the squid process took at least
> 50% while handling the same amount of traffic. The configuration was
> identical.
> Regards
> Henri
>
Check the disk loading and cache.log entries for store rebuild
messages. 3.2 has a new cache format and requires a full cache rebuild
scan after upgrade from any older Squid. This can consume a lot of CPU
until the scan is completed then is expected to drop back to same or
less CPU than 3.1.
Amos
Received on Tue May 08 2012 - 22:26:10 MDT
This archive was generated by hypermail 2.2.0 : Thu May 10 2012 - 12:00:05 MDT