[squid-users] Tune Squid proxy to handle 90k connection

[André Bolinhas]

Any tip about my last comment?

-----Mensagem original-----
De: André Bolinhas <andre.bolinhas at articatech.com> 
Enviada: 21 de janeiro de 2022 16:36
Para: 'Amos Jeffries' <squid3 at treenet.co.nz>; squid-users at lists.squid-cache.org
Assunto: RE: [squid-users] Tune Squid proxy to handle 90k connection

Thanks Amos
Yes, you are right, I will put a second box with HaProxy in front to balance the traffic.
About the sockets I can't double it because is a physical machine, do you think disable hyperthreading from bios will help, because we have other services inside the box that works in multi-threading, like unbound DNS?

Just more a few questions:
1º The server have 92Gb of Ram, do you think that is needed that adding swap will help squid performance?
2º Right now we are using squid 4.17 did you recommend upgrade or downgrade to any specific version?
3º We need categorization, for this we are using an external helper to achieve it, do you recommend use this approach with ACL or move to some kind of ufdbguard service?

Best regards
-----Mensagem original-----
De: squid-users <squid-users-bounces at lists.squid-cache.org> Em Nome De Amos Jeffries
Enviada: 21 de janeiro de 2022 16:05
Para: squid-users at lists.squid-cache.org
Assunto: Re: [squid-users] Tune Squid proxy to handle 90k connection

Sorry for the slow reply. Responses inline.


On 14/01/22 05:44, André Bolinhas wrote:
> Hi
> ~80k request per second  10k users


Test this, but you may need a second machine to achieve the full 80k RPS.

Latest Squid do not have any details analysis, but older Squid-3.5 were only achieving >15k RPS under lab conditions, more likely expect under 10k RPS/worker on real traffic.
  That means (IME) this machine is quite likely to hit its capacity somewhere under 70k RPS.


> CPU info:
> CPU(s) 16
> Threads per code 2
> Cores per socket 8

With this CPU you will be able to run 7 workers. Setup affinity of one core per worker (the "kidN" processes of Squid). Leaving one core to the OS and additional processing needs - this matters at peak loading.

CPU "threads" tend not to be useful for Squid. Under high loads Squid workers will consume all available cycles on their core, not leaving any for the fancy "thread" core sharing features to pretend there is another core available. YMMV. One of the tests to try when tuning is to turn off the CPU hyperthreading and see what effect it has (if any).


> Sockets 1
> Inter Xeron Silver 4208  @ 2.10GHz
>

Okay. Doable, but for best performance you want as high GHz rating on the cores as your budget can afford. The amount of "lag" Squid adds to traffic and RPS performance/parallelism directly correlates with how fast the CPU core can run cycles.



HTH
Amos
_______________________________________________
squid-users mailing list
squid-users at lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users