Search squid archive

Running SMP workers on multi-core systems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I am trying to use the squid cache as an outbound HTTP/S proxy service for our production network and would like to scale up the request per sec by running it on multi-core systems. 

I have searched up the archives and config docs, but couldn't find anything more recent than the below on setting up SMP workers. 
https://wiki.squid-cache.org/ConfigExamples/SmpCarpCluster
https://wiki.squid-cache.org/ConfigExamples/MultiCpuSystem

* Can someone please let me know if the config examples in those docs still apply to the latest version 5.1.

* Do we still need the combination of squid, frontend, backend.conf files, or is it enabled simply with the "workers" line in the main config file? 

* When I attempt to run the squid server with "workers 4" in the squid.conf, I get the following error (one for each kid) and the main process does not bind to the "http_port 3128". I see several UDP ports opened up for each kid process.
2021/09/29 00:44:10 kid5| commBind Cannot bind socket FD 11 to [::]: (2) No such file or directory
* Does anyone have recommendations on the maximum number of workers to use on a 64 core host (assuming no other CPU intensive apps are running on the same host). Caching is not a must for our initial deployment, so we are fine disabling caching.

Thanks
Praveen


_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux