Never mind. The problem was that I didn't have gcc-c++ installed. Not sure why
it threw the valgrind header error message but oh well. I am building now. Will
hopefully have some valgrind data soon.
Thanks
-Ty
Running into a problem.
Installed valgrind and valgrind-devel packages via yum.
Tried to build squid with:
./configure --prefix=/usr/local/squid --with-valgrind-debug
--sysconfdir=/etc/squid --with-logdir=/var/log/squid
--with-pidfile=/var/run/squid.pid --with-swapdir=/srv/proxy/cache
--enabl
> did you tune the tcp timing on the machine? time_wait? close ? etc...
No, tcp timing is CentOS default which should be fine for a server at this
utilization
> the timeout can be really off the chart sometimes leaving you with hundreds
> if not K's of connections open for a reason and will make
On 27.09.2012 10:37, t...@raynersw.com wrote:
NP: its about time we ran 3.2 through another valgrind session, your
traffic looks high enough to provide useful details. If you are happy
to do this the valgrind report will be welcomed on the squid-dev
mailing list.
Sure, I'd be glad to. Thanks
On 9/27/2012 12:13 AM, t...@raynersw.com wrote:
Just wish I had some squid development experience so I could easily get into a
debugging environment and track this down... but squid's a big package and I
know there will be a big learning curve to start debugging builds.
Thanks
-Ty
you dont jum
I did find the wiki, sorry:
http://wiki.squid-cache.org/ProgrammingGuide/LeakHunting
Are these still the relevant steps for 3.2.1?
> NP: its about time we ran 3.2 through another valgrind session, your traffic
> looks high enough to provide useful details. If you are happy to do this the
> valgrind report will be welcomed on the squid-dev mailing list.
Sure, I'd be glad to. Thanks for the help. Awesome debug on the 32/64 ma
On 27.09.2012 07:09, t...@raynersw.com wrote:
Hi Eliezer,
Thanks for the feedback. This memory leak causes real-world problems
for me, as squid starts to do a lot of swapping when it exhausts
physical RAM, and things slow down. Also, the sheer magnitude of the
memory numbers is just ridiculous..
And as an aside- I have no idea what I did to post this at the end of somebody
else's thread instead of making a new topic, but that was clearly my bad.
-Ty
Thanks- that is good to hear that you've seen heavier-load installations than
mine that don't exhibit the problem. Were any of them running on Linux x86_64?
Maybe that's the culprit. There must be some combination of factors.
It's just strange because I don't think there's anything all that weir
On 9/26/2012 11:28 PM, t...@raynersw.com wrote:
Regarding the config directives, I have tried changing the values of those in
the past, but really the defaults are very conservative so they shouldn't be
responsible for all this memory usage, unless the default is being ignored and
treated as u
Thanks. The thing is, I don't even think an iptables ACL will fix this leak,
because I have other squid processes running without a lengthy ACL (using an
auth program instead) and they too exhibit the leak.
Squid on most of my servers is from the standard CentOS 6.3 package.
Compilation options
On 9/26/2012 9:09 PM, t...@raynersw.com wrote:
Hi Eliezer,
Thanks for the feedback. This memory leak causes real-world problems for me, as
squid starts to do a lot of swapping when it exhausts physical RAM, and things
slow down. Also, the sheer magnitude of the memory numbers is just
ridiculo
Hi Eliezer,
Thanks for the feedback. This memory leak causes real-world problems for me, as
squid starts to do a lot of swapping when it exhausts physical RAM, and things
slow down. Also, the sheer magnitude of the memory numbers is just
ridiculous... squid easily grows to in excess of 10GB of
On 9/26/2012 8:11 PM, t...@raynersw.com wrote:
Reposting this because I posted the original via the nabble site and it didn't
get mailed out to the list
I posted a while ago about this but didn't get any replies. I run squid servers
which handle heavy sustained traffic (50-100Mbps per ser
Reposting this because I posted the original via the nabble site and it didn't
get mailed out to the list
I posted a while ago about this but didn't get any replies. I run squid servers
which handle heavy sustained traffic (50-100Mbps per server is not unusual).
The squid processes' memory
16 matches
Mail list logo
