> Thanks. The current maximum_object_size_in_memory is 19 MB.
>
>>
>> In summary, dealing with in-RAM objects significantly larger than 1MB
>> bigger the object, the longer Squid takes to scan its nodes.
>>
>> Short term, try limiting the size of in-RAM objects using
>>
On 2016-03-31 16:21, sq...@peralex.com wrote:
> On 2016-03-31 16:07, Yuri Voinov wrote:
>>
>> Looks like permanently running clients, which is exausted network
>> resources and then initiating connection abort.
>>
>> Try to add
>>
>> client_persistent_connections off
This option didn't fix the
On 2016-03-31 18:44, Alex Rousskov wrote:
>
> My working theory is that the longer you let your Squid run, the bigger
> objects it might store in RAM, increasing the severity of the linear
> search delays mentioned below. A similar pattern may also be caused by
> larger objects becoming more
On 03/31/2016 07:53 AM, sq...@peralex.com wrote:
> Every week or so I run into a problem where squid's CPU usage starts
> growing slowly, reaching 100% over the course of a day or so. When
> running normally its CPU usage is usually less than 5%. Restarting
> squid fixes the problem.
My
On 2016-03-31 16:07, Yuri Voinov wrote:
>
> Looks like permanently running clients, which is exausted network
> resources and then initiating connection abort.
>
> Try to add
>
> client_persistent_connections off
>
> to squid.conf.
>
> Then observe.
Thanks.
I added it and run squid -k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Looks like permanently running clients, which is exausted network
resources and then initiating connection abort.
Try to add
client_persistent_connections off
to squid.conf.
Then observe.
31.03.16 19:53, sq...@peralex.com пишет:
> Hi,
>
> I'm
Hi,
I'm running:
Squid Cache: Version 3.5.15 (including patches up to revision 14000)
on FreeBSD 9.3-STABLE (recently updated)
Every week or so I run into a problem where squid's CPU usage starts
growing slowly, reaching 100% over the course of a day or so. When
running normally its CPU
