[squid-users] MAXHTTPORTS CentOS 6

[Eliezer Croitoru]

OK so I will stick with the default since it makes more sense that it fit's most of the regular use cases.
If someone needs a special build he should be able to handle a self compiled squid.

Thanks,
Eliezer

----
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: eliezer at ngtech.co.il


-----Original Message-----
From: Amos Jeffries [mailto:squid3 at treenet.co.nz] 
Sent: Tuesday, April 4, 2017 3:01 AM
To: Eliezer Croitoru <eliezer at ngtech.co.il>; squid-users at lists.squid-cache.org
Subject: Re: [squid-users] MAXHTTPORTS CentOS 6

On 4/04/2017 7:39 a.m., Eliezer  Croitoru wrote:
> Amos still the question in hands is very simple:
> Would it matter if I will upper the limit to 16384?
> For example would it result in some memory overhead?

The usual answer applies - "it depends".

Some of the I/O modules (eg select and poll) require each special port to be explicitly polled once every 10ms. The epoll/kqueue etc, only poll them when other things do I/O and no less than every 10ms. So you need a very fast server or it will kill performance for anything else.

And yes, having configuration state for each port means a lot more memory used. These daya the use of TLS on ports means OpenSSL loads the full set of trusted CAs into that state. So it can get VERY huge for no obvious reason.

I dont think it is wise to embed larger limits. The one we have is an order of magnitude larger than necessary for most installs. So it is not generally useful.

All of the above is why there is no ./configure option. But there have been a handful of queries wanting more, so the build option is conditional.

HTH
Amos