I didn't change my config at all, so I'm fairly sure it's simply
updating to 3.3.8 that fixed it for me. All I did was change to Testing
and do apt-get dist-upgrade.
Maybe Debian compile it differently to Ubuntu - This is what Debian's
version tells me:
Squid Cache: Version 3.3.8
configure options: '--build=i486-linux-gnu' '--prefix=/usr'
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
'--infodir=${prefix}/share/info' '--sysconfdir=/etc'
'--localstatedir=/var' '--libexecdir=${prefix}/lib/squid3' '--srcdir=.'
'--disable-maintainer-mode' '--disable-dependency-tracking'
'--disable-silent-rules' '--datadir=/usr/share/squid3'
'--sysconfdir=/etc/squid3' '--mandir=/usr/share/man' '--enable-inline'
'--enable-async-io=8' '--enable-storeio=ufs,aufs,diskd,rock'
'--enable-removal-policies=lru,heap' '--enable-delay-pools'
'--enable-cache-digests' '--enable-underscores' '--enable-icap-client'
'--enable-follow-x-forwarded-for'
'--enable-auth-basic=DB,fake,getpwnam,LDAP,MSNT,MSNT-multi-domain,NCSA,NIS,PAM,POP3,RADIUS,SASL,SMB'
'--enable-auth-digest=file,LDAP'
'--enable-auth-negotiate=kerberos,wrapper'
'--enable-auth-ntlm=fake,smb_lm'
'--enable-external-acl-helpers=file_userip,kerberos_ldap_group,LDAP_group,session,SQL_session,unix_group,wbinfo_group'
'--enable-url-rewrite-helpers=fake' '--enable-eui' '--enable-esi'
'--enable-icmp' '--enable-zph-qos' '--enable-ecap'
'--disable-translation' '--with-swapdir=/var/spool/squid3'
'--with-logdir=/var/log/squid3' '--with-pidfile=/var/run/squid3.pid'
'--with-filedescriptors=65536' '--with-large-files'
'--with-default-user=proxy' '--enable-linux-netfilter'
'build_alias=i486-linux-gnu' 'CFLAGS=-g -O2 -fPIE -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall'
'LDFLAGS=-fPIE -pie -Wl,-z,relro -Wl,-z,now'
'CPPFLAGS=-D_FORTIFY_SOURCE=2' 'CXXFLAGS=-g -O2 -fPIE -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security'
TB
On 7/09/2013 5:22 PM, Mohsen Dehghani wrote:
Hello
I have the same CPU problem with 3.3.8. would you please share your
experience with me?
Previously I was using 3.1.19(default Ubuntu repository) with no CPU
problem. But it lacks some new features that is included in newer versions.
I have done so many test on a VM. This is the testing process:
Installed Ubuntu12.04---------create SNAPSHOT_1----------install
3.1.19-----------put load(150Mbps)==30%CPU without any drop in bandwidth
graph
Moving back to SNAPSHOT_1---------install 3.3.8----------- put
load(150Mbps)==100%CPU with sudden drop in bandwidth graph
It is now clear for me that 3.3.8 cannot cope with the load due to: 1-my
wrong configuration 2-my wrong compilation 3-or some problems in squid
Thanks
-----Original Message-----
From: Tim Bates [mailto:tin@xxxxxxxxxxxxxxx]
Sent: Saturday, September 07, 2013 8:46 AM
To: squid-users@xxxxxxxxxxxxxxx
Subject: Re: 100% CPU when bigger files are downloading
For anyone who's interested, I upgraded to Debian Testing a few days ago,
and to their build of 3.3.8 - problem has been solved.
TB
On 3/08/2013 5:52 PM, Tim Bates wrote:
On 24/07/2013 2:01 PM, Tim Bates wrote:
OK, so I've got Squid 3.1.6 (from Debian Wheezy) running on a OpenVZ
container.
OK, so I discovered I was actually running Squeeze still (which has
3.1.6). I upgraded to Wheezy (has Squid 3.1.20) hoping it would fix
it, but no... Still runs at 100% CPU during downloads.
I also attempted to compile my own 3.3.x the other day. This went
quite badly. The builds I ended up with all just crashed before
anything even got a chance to connect.
I did try Squid 2.x just to check things are OK in that, and it seemed
to work fine. I think I'll just move everything over to use 2.x
instead for now.
TB
