On 10.03.17 08:52, Alex Rousskov wrote:
Sorry, but that 2010 documentation is outdated. It was written before
Rock store, a 2011 feature that changed what "SMP mode" means. This is
my fault. Here is a replacement draft that I was working on until wiki
went down:
NAME: workers
DEFAULT: 1
On 03/20/2017 09:20 AM, Matus UHLAR - fantomas wrote:
> On 10.03.17 08:52, Alex Rousskov wrote:
>> Sorry, but that 2010 documentation is outdated. It was written before
>> Rock store, a 2011 feature that changed what "SMP mode" means. This is
>> my fault. Here is a replacement draft that I was
On 10.03.17 08:52, Alex Rousskov wrote:
Sorry, but that 2010 documentation is outdated. It was written before
Rock store, a 2011 feature that changed what "SMP mode" means. This is
my fault. Here is a replacement draft that I was working on until wiki
went down:
NAME: workers
DEFAULT: 1
On 03/10/2017 02:38 AM, Matus UHLAR - fantomas wrote:
>> On 03/09/2017 10:24 AM, Matus UHLAR - fantomas wrote:
>>> is running aufs with rock store and safe, when not running with "-N"?
>
> On 09.03.17 11:02, Alex Rousskov wrote:
>> Running AUFS in SMP mode is unsafe by default but some admins use
o.il
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Amos Jeffries
Sent: Thursday, March 9, 2017 6:36 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] squid workers question
On 10/03/2017 5:19 a.m., Matus UHLAR - fantoma
On 03/09/2017 10:24 AM, Matus UHLAR - fantomas wrote:
is running aufs with rock store and safe, when not running with "-N"?
On 09.03.17 11:02, Alex Rousskov wrote:
Running AUFS in SMP mode is unsafe by default but some admins use
configuration hacks to make it work for them. Primary Store
On 03/09/2017 10:24 AM, Matus UHLAR - fantomas wrote:
>> On 03/09/2017 09:54 AM, Matus UHLAR - fantomas wrote:
>> Master is not a
>> kid (it is a parent of all kids), the first N kids are workers, the
>> next D kids are diskers, and the last kid is Coordinator. Please
>> see the
On 03/09/2017 10:18 AM, Matus UHLAR - fantomas wrote:
> cache_dir rock /var/spool/squid3/rock 1024 max-size=32768
> #cache_dir aufs /var/spool/squid3 8192 16 256 min-size=32769
>
> are those correct values? (bug 3411 says something about 256B
> metadata)
>>>
Those 256 Byte
On 03/09/2017 09:54 AM, Matus UHLAR - fantomas wrote:
Master is not a
kid (it is a parent of all kids), the first N kids are workers, the
next D kids are diskers, and the last kid is Coordinator. Please see the
following wiki section for more details.
On 10.03.17 05:30, Amos Jeffries wrote:
seems that my memory problem is somehow related to 4g of "2K Buffers"
whatever that means. This is cachrmgr output:
(bytes)KB/chobj/ch(#)usedfreepart
%Frag(#)(KB)high (KB)high (hrs)%Tot(#)
(KB)
On 03/09/2017 09:54 AM, Matus UHLAR - fantomas wrote:
Master is not a
kid (it is a parent of all kids), the first N kids are workers, the
next D kids are diskers, and the last kid is Coordinator. Please see the
following wiki section for more details.
On 09.03.17 09:07, Alex Rousskov wrote:
Both rock and AUFS stores support large objects so there is no
requirement to split storage based on object sizes. Each store has
various pros and cons, but lack of large object support is not one of
the distinguishing characteristics.
I thought the
On 03/09/2017 09:19 AM, Matus UHLAR - fantomas wrote:
> On 09.03.17 09:07, Alex Rousskov wrote:
>> Both rock and AUFS stores support large objects so there is no
>> requirement to split storage based on object sizes. Each store has
>> various pros and cons, but lack of large object support is not
On 10/03/2017 5:19 a.m., Matus UHLAR - fantomas wrote:
>> On 03/09/2017 07:21 AM, Matus UHLAR - fantomas wrote:
>>> I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie
>>> version)
>>>
>>> (I know it's old, but I prefer using distribution-provided SW unless
>>> it has
>>> real
On 10/03/2017 5:14 a.m., Matus UHLAR - fantomas wrote:
>> On 10/03/2017 3:21 a.m., Matus UHLAR - fantomas wrote:
>>> I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie
>>> version)
>
>>> - does this version have known memory leaks?
>>>
On 03/09/2017 07:21 AM, Matus UHLAR - fantomas wrote:
I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie
version)
(I know it's old, but I prefer using distribution-provided SW unless it has
real problem distribution isn't able to fix)
On 09.03.17 09:07, Alex Rousskov wrote:
On 10/03/2017 3:21 a.m., Matus UHLAR - fantomas wrote:
I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie
version)
- does this version have known memory leaks?
http://www.squid-cache.org/Versions/v3/3.5/ChangeLog.txt
shows some leaks fixed but they all seem to be related to
On 03/09/2017 07:21 AM, Matus UHLAR - fantomas wrote:
> I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie
> version)
>
> (I know it's old, but I prefer using distribution-provided SW unless it has
> real problem distribution isn't able to fix)
My answers are based on v5 code.
On 10/03/2017 3:21 a.m., Matus UHLAR - fantomas wrote:
> Hello,
>
> I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie
> version)
>
> (I know it's old, but I prefer using distribution-provided SW unless it has
> real problem distribution isn't able to fix)
>
> - does this
Hello,
I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie version)
(I know it's old, but I prefer using distribution-provided SW unless it has
real problem distribution isn't able to fix)
- does this version have known memory leaks?
20 matches
Mail list logo
