-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/11/2014 4:12 a.m., Rietzler, Markus (RZF, SG 324 / <RIETZLER_SOFTWARE>) wrote: >> -----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... The only difference between SMP and non-SMP mode here is that non-SMP has 1 worker doing all the work with one CPU core, whereas SMP mode has several workers. They can all hit the same issues independently for the same reason(s). I am of the understanding that the code associated with the helper processe is using a lot of CPU doing *something* that consumes a lot of cycles. There is a bunch of code doing cache lookups on previous helper queries, queueing new lookups, generating and parsing strings in the I/O, and even sometimes running whole trees of ACL logics when the helper(s) respond. So to get anywhere on this complaint it is important to know what (from the above set of things) exactly the CPU is doing. Amos -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUYODRAAoJELJo5wb/XPRjvrkH/RBEitKpvLcWypNPCCrMTtw6 tKftf9gz4og6GOkUiipE0qNLTMgWvV7Fk9/By3vhEGNL+WpQG5UEWCbfpc2h2RdL H5tIWJGnXcsV1PGwYI1cuyDpanNs6EnSvKnSGTZ2DdWabiFEOPr9FR/8QtVqpUdS EK3uMpnmZ0mbo7auDIPxwa7CYh44tC/C3VMZSto+peB1ikiDonU9B0tXVEFCheeE B0IWs8FaoYByVd54lL6cYPz7HcOtyt2Hb6uyPJyQVrrEJs2JuI4ZQh0X7B2mbzAi HK8wBbDcyC4ZKagq4ABQIYHsxwqxiNFD6v9ntXBjZpORG1opXLMSBAh9K0Ycq5s= =5pNQ -----END PGP SIGNATURE----- _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
