> -----Ursprüngliche Nachricht----- > Von: squid-users [mailto:squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx] Im > Auftrag von Amos Jeffries > Gesendet: Montag, 10. November 2014 14:36 > An: squid-users@xxxxxxxxxxxxxxxxxxxxx > Betreff: Re: High CPU-Usage with squid 3.4.9 (and/or > 3.4.4) > > On 7/11/2014 2:50 a.m., Tom Tom wrote: > > Hi > > > > After migration from squid 3.3.13 to 3.4.4, I recognized a > > performance-issue. Squid is configured with 4 workers. They often > > have a CPU-Utilization between 50%-90% (each worker). With squid > > 3.3.13 (same configuration), the CPU-Utilization was never a > > problem. I installed squid 3.4.9 and had the same issue. No > > warnings/errors in the cache.log > > > > I saw, that someone other reported a similar issue: > > http://www.squid-cache.org/mail-archive/squid-users/201407/0500.html > > > > Concerning the post above: Yes, we have external_auth-helpers > > (ext_kerberos_ldap_group_acl) and no, we do not use delay_pools. > > The high cpu-usage comes not from the auth-helper - it comes from > > the 4 squid-worker-processes. Any hints? Is this a known problem? > > Probably solved in 3.5? > > Are you able to find out any specific details about what the workers > are doing that uses so much extra CPU? > > Amos > during our last tests (with 3.4.x) we also tried the worker option. it does not matter if workers are enabled or not. with more workers the cpu rise seems to be somewhat slower. so it is not connected to (smp)workers. it is the external auth helper - although the squid process and not the helper does consume all the cpu... markus _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
