Le 19/08/2017 à 22:08, Eliezer Croitoru a écrit :
> Hey Emmanuel,
>
> Something is not clear to me.
> Are you using url_rewrite or store_id helpers in any form?
No
> Also what DNS lookups squid does exactly?
> - Reverse
> - Forward
Mostly forward
>
> Also:
> - internal clients
> - external domains
-28704261
Email: elie...@ngtech.co.il
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of FUSTE Emmanuel
Sent: Friday, August 18, 2017 14:53
To: Amos Jeffries ; squid-users@lists.squid-cache.org
Subject: [squid-users] Memory leak (was: Squid 3.x
Le 24/01/2017 à 10:55, FUSTE Emmanuel a écrit :
> Le 23/01/2017 à 23:41, Amos Jeffries a écrit :
>> On 24/01/2017 3:58 a.m., FUSTE Emmanuel wrote:
>>> All was carefully checked and nothing in my configuration (acl etc ...)
>>> explain why Squid insist to do DNS requests for requests forwarded to
>>
Hi.
On 12.01.2015 19:06, Amos Jeffries wrote:
>
> I am confident that those types of leaks do not exist at al in Squid 3.4.
>
> These rounds of mmory exhaustion problems are caused by pseudo-leaks,
> where Squid incorrectly holds onto memory (has not forgotten it
> though) far longer than it shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/01/2015 1:15 a.m., Yuri Voinov wrote:
>
> Yep.
>
> Memory leaking - if it really it - will be occurs on all
> platforms.
>
> If not - this is OS-specific issue. libc, malloc library problem.
> But not squid itself.
>
By definition a memory l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yep.
Memory leaking - if it really it - will be occurs on all platforms.
If not - this is OS-specific issue. libc, malloc library problem. But
not squid itself.
12.01.2015 18:06, Eugene M. Zheganin пишет:
> Hi.
>
> On 12.01.2015 16:41, Eugene M.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yep.
Memory leaking - if it really it - will be occurs on all platforms.
If not - this is OS-specific issue. libc, malloc library problem. But
not squid itself.
12.01.2015 18:06, Eugene M. Zheganin пишет:
-BEGIN PGP SIGNATURE-
Version:
Hi.
On 12.01.2015 16:41, Eugene M. Zheganin wrote:
> I'm now also having a strong impression that squid is leaking memory.
> Now, when 3.4.x is able to handle hundreds of users during several
> hours I notice that it's memory usage is constantly increasing. My
> patience always ends at the point o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like an OS-specific issue.
I don't see any memory leaking on my boxes (running Solaris 10, yes ;)).
Moreover, helpers is corrrectly got an release memory.
12.01.2015 17:41, Eugene M. Zheganin пишет:
> Hi.
>
> On 09.01.2015 06:12, Amos Jeffrie
Hi.
On 09.01.2015 00:10, Doug Sampson wrote:
> Man, I empathize with you. Have you tried running Squid 3.4.x on
> FreeBSD 9.3? Sometimes I wonder if it's FreeBSD 10.x that's causing
> the issue...
It's not. FreeBSD 9.x branch was a crappy release from it's start.
Eugene.
_
Hi.
On 09.01.2015 06:12, Amos Jeffries wrote:
> Grand total:
> => 9.5 GB of RAM just for Squid.
>
> .. then there is whatever memory the helper programs, other software
> on the server and operating system all need.
>
I'm now also having a strong impression that squid is leaking memory.
Now, whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/01/2015 8:10 a.m., Doug Sampson wrote:
>> Hi,
>>
>> I have the similar problem on FreeBSD 10.1-STABLE #1 r275861
>> with squid-3.4.10. I also applied MEMPOOLS=1 when starting squid.
>> I experience the process slowing down and unacceptable
>> per
> Doug Sampson writes:
>> Hi,
>>
>> I have the similar problem on FreeBSD 10.1-STABLE #1 r275861 with
>> squid-3.4.10. I also applied MEMPOOLS=1 when starting squid. I
>> experience the process slowing down and unacceptable performance.
>>
>> Squid is configured
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I mean,
cache_mem is too big.
First, 600 users is not very big installation to do huge memory cache.
1-2 Gb will be ehough. With fast disk cache.
Second - 4 Gb ram is near 32-bit address limit. Possible 32-bit library
or somewhat meets this limit.
> Hi,
>
> I have the similar problem on FreeBSD 10.1-STABLE #1 r275861 with
> squid-3.4.10. I also applied MEMPOOLS=1 when starting squid. I
> experience the process slowing down and unacceptable performance.
>
> Squid is configured to use kerberos and ntlm authentication and lap
> group authenti
Hi,
I have the similar problem on FreeBSD 10.1-STABLE #1 r275861 with
squid-3.4.10. I also applied MEMPOOLS=1 when starting squid. I
experience the process slowing down and unacceptable performance.
Squid is configured to use kerberos and ntlm authentication and lap
group authentication. other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2014 4:22 a.m., Doug Sampson wrote:
>> Nothing particularly stands out as leaking. Although the cache
>> memory pages (mem_node) in-use size is suspiciously close to half
>> what you say the OS is reporting.
>>
>> That makes me suspect that y
> Nothing particularly stands out as leaking. Although the cache memory
> pages (mem_node) in-use size is suspiciously close to half what you
> say the OS is reporting.
>
> That makes me suspect that your OS is rounding up its allocations to
> 8KB of memory for each node. If that is the case the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/12/2014 11:17 a.m., Doug Sampson wrote:
>> On 26/11/2014 8:59 a.m., Doug Sampson wrote:
>>>
>>> Thanks, Amos, for your pointers.
>>>
>>> I've commented out all the fresh_patterns lines appearing
>>> above the last two lines.
>>>
>>> I also have
> On 26/11/2014 8:59 a.m., Doug Sampson wrote:
> >
> > Thanks, Amos, for your pointers.
> >
> > I've commented out all the fresh_patterns lines appearing above
> > the last two lines.
> >
> > I also have dropped diskd in favor of using aufs exclusively,
> > taking out the min-size parameter. I've c
I used the ugly tuning: set vm.defer_swapspace_pageouts to 1. But it
is may caused some issue when the physic memory is really exhausted. I
have no much time to investigate the right way, but I think maybe
vm.swap_idle_threshold1/vm.swap_idle_threshold2 or vm.overcommit etc.
maybe harmful.
>Maybe your problem is related to sysctl mib tuning about
> swap/overcommit etc. I did not observed memory leak with squid 3.4.4,
> but FB 10 do swap frequently than old version.
Could you elaborate a bit more? That went over my head. What could I do in
terms of tuning the system?
~Doug
Maybe your problem is related to sysctl mib tuning about
swap/overcommit etc. I did not observed memory leak with squid 3.4.4,
but FB 10 do swap frequently than old version.
Simon
___
squid-users mailing list
squid-users@lists.squid-cache.org
http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/11/2014 8:59 a.m., Doug Sampson wrote:
>
> Thanks, Amos, for your pointers.
>
> I've commented out all the fresh_patterns lines appearing above
> the last two lines.
>
> I also have dropped diskd in favor of using aufs exclusively,
> taking ou
> On 25/11/2014 9:06 a.m., Doug Sampson wrote:
> > Recently due to squid 2.7 being EOL'ed, we migrated our squid
> > server to version 3.4.9 on a FreeBSD 10.0-RELEASE running on 64-bit
> > hardware. We started seeing paging file being swapped out
> > eventually running out of available memory. From
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/11/2014 9:06 a.m., Doug Sampson wrote:
> Recently due to squid 2.7 being EOL'ed, we migrated our squid
> server to version 3.4.9 on a FreeBSD 10.0-RELEASE running on 64-bit
> hardware. We started seeing paging file being swapped out
> eventually
Recently due to squid 2.7 being EOL'ed, we migrated our squid server to version
3.4.9 on a FreeBSD 10.0-RELEASE running on 64-bit hardware. We started seeing
paging file being swapped out eventually running out of available memory. From
the time squid gets started it usually takes about two days
27 matches
Mail list logo
