On 3/6/19 11:25 AM, George Xie wrote:
>> So disabling swap entirely on the server is not a great idea. It just
>> moves the error and shutdown to happen at peak traffic times when it is
>> least wanted.
> but I guess this is common in the "cloud" era, eg: Google Compute Engine.
Moreover, in many
thanks for your detailed reply, Amos.
now I have found out the culprit is large file descriptor number limit.
Docker CE for Debian package has set this limit (RLIMIT_NOFILE) in the
container to 1048576, thus squid set Squid_MaxFD to 1048576, then
allocates 1048576*392 = 392m memory for `fd_table`.
On 3/4/19 9:45 PM, George Xie wrote:
> #4 0x558a3d0a in comm_init () at comm.cc:1206
> 1206fd_table =(fde *) xcalloc(Squid_MaxFD, sizeof(fde));
> (gdb) p Squid_MaxFD
> $1 = 1048576
> (gdb) p sizeof(fde)
> $2 = 392
>
> It seems Squid_MaxFD is way too large, and its value is direct
On 4/03/19 9:45 pm, George Xie wrote:
> > On 4/03/19 5:39 pm, George Xie wrote:
> > > hi all:
> > >
> > > Squid version: 3.5.23-5+deb9u1
> > > Docker version 18.09.3, build 774a1f4
> > > Linux instance-4 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
> > > x86_64 GNU
more detail of the backtrace:
(gdb) up
#4 0x558a3d0a in comm_init () at comm.cc:1206
1206fd_table =(fde *) xcalloc(Squid_MaxFD, sizeof(fde));
(gdb) p Squid_MaxFD
$1 = 1048576
(gdb) p sizeof(fde)
$2 = 392
It seems Squid_MaxFD is way too large, and its value is directly from ulimit
> To correct that default
> behavior, add this:
> cache_mem 0
thanks for your advice, but actually, I have tried this option before,
found no difference. besides, and I have tried `memory_pools off`.
> Furthermore, older Squids, possibly including your no-longer-supported
> version, may allocat
On 3/3/19 9:39 PM, George Xie wrote:
Squid version: 3.5.23-5+deb9u1
debian 9, currently stable, soon to be replaced by debian 10, containing
squid-4.4
http_port 127.0.0.1:3128
cache deny all
access_log none
On 04.03.19 09:34, Alex Rousskov wrote:
Unfortunately, this configurati
On 3/3/19 9:39 PM, George Xie wrote:
> Squid version: 3.5.23-5+deb9u1
> http_port 127.0.0.1:3128
> cache deny all
> access_log none
Unfortunately, this configuration wastes RAM: Squid is not yet smart
enough to understand that you do not want any caching and may allocate
256+ MB of m
>
> > On 4/03/19 5:39 pm, George Xie wrote:
> > > hi all:
> > >
> > > Squid version: 3.5.23-5+deb9u1
> > > Docker version 18.09.3, build 774a1f4
> > > Linux instance-4 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
> > > x86_64 GNU/Linux
> > >
> > > I have the following squid config:
> > >
> >
On 4/03/19 5:39 pm, George Xie wrote:
> hi all:
>
> Squid version: 3.5.23-5+deb9u1
> Docker version 18.09.3, build 774a1f4
> Linux instance-4 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
> x86_64 GNU/Linux
>
> I have the following squid config:
>
>
> http_port 127.0.0.1:3128
> cac
10 matches
Mail list logo
