[squid-users] 3.3.x -> 3.4.x: huge performance regression

[Eugene M. Zheganin]

Hi.

On 24.10.2014 17:17, Rietzler, Markus (RZF, SG 324 /
<RIETZLER_SOFTWARE>) wrote:
> the important keyword is "NTLM"! 
> without external auth helper squid 3.4 is working well. as soon as the external helper is active, cpu rises to 100%. nothing with workers etc.
> even the fakehelper is not working. just to make sure, that the problem is not NTLM, samba, winbind, AD etc.
>
> see http://bugs.squid-cache.org/show_bug.cgi?id=3997
There seems to be a large mix of terms, like "external helper" and
"external program". The ntlm_auth, which is external to squid and part
of the samba package, doesnt' change between version uprgrades, so I
don't see how it can be involved (and why replace it with a fake helper
?). In the same time it's an authentication helper. The squid_kerb_ldap,
also known as ext_kerberos_ldap_group_acl, is, indeed, an "external acl"
helper, but it has nothing to do with NTLM, as it doesn't use it. My
opinion - this pr is flooded with error messages of almost any kind, and
it's very hard to see the point.

We need to understand what's happening to squid when it starts to hit
the 100% CPU usage, last time I saw this during the night without any
possible user traffic load.

Eugene.