[squid-users] Squid memory leak on ubuntu 14.04

2015-11-27 Thread
Hi, We had installed squid 3.3.8 on ubuntu 12.04, when we upgrade the OS from ubuntu 12.04 to 14.04, we found the memory usage abnormal, eat up all memory. After we investigation: We use 4 servers for comparision: 3.3.8 on ubuntu 12.04 3.5.11 on ubuntu 12.04 3.3.8 on ubuntu 14.04 3.5.11 on ubu

Re: [squid-users] Squid memory leak on ubuntu 14.04

2015-11-29 Thread
the resident memory is what you expect > that Squid uses (comparable as on 12.04) and the virtual memory is high. > This is the new "normal" behavior of malloc. > > Marcus > > > On 11/27/2015 01:41 PM, 风声 wrote: > >> Hi, >> >> We had installed squid 3

Re: [squid-users] Squid memory leak on ubuntu 14.04

2015-11-30 Thread
with squid-3.3.8 (ubuntu offical packages), and squid-3.5.11 on 12.04 and 14.04, I think it is most likely ubuntu related issue ? because same version, same configs, but different OS versions. 2015-11-30 11:37 GMT+08:00 Amos Jeffries : > On 30/11/2015 3:19 p.m., 风声 wrote: > > I t

Re: [squid-users] Squid memory leak on ubuntu 14.04

2015-11-30 Thread
2015-11-30 16:55 GMT+08:00 Amos Jeffries : > On 30/11/2015 9:31 p.m., 风声 wrote: > > We did not enable squid cache, so I think memory is ok for our case, and > we > > run squid servers (without cache, without cache cluster, just as forward > > proxy) more than 100 ser

[squid-users] How to use the different Store ID with same url and different proxy port ?

2015-11-30 Thread
Hi, We want to Squid-3 to listen serveral ports (like 3128/3129/3120/...), but we want reply different cached objects for different ports with same request (same url), because we want to cache compressed objects for some ports. How can we do that ? we try to use store id configs in squid.conf, bu

Re: [squid-users] Squid memory leak on ubuntu 14.04

2015-12-02 Thread
I think not only the kernel/malloc, also the libs (libmnl and libnetfilter) squid depends on with ubuntu 14.04, we try to rebuild it, keep watching the status. 2015-12-01 9:01 GMT+08:00 风声 : > Hi > > Finally, we found the root cause, it is kernel issue with specific version > on