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

[Amos Jeffries]

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