[squid-dev] Benchmarking Performance with reuseport

Amos Jeffries squid3 at treenet.co.nz
Thu Aug 4 11:12:36 UTC 2016

On 4/08/2016 8:48 a.m., Marcus Kool wrote:
> https://www.nginx.com/blog/socket-sharding-nginx-release-1-9-1/
> is an interesting short article about using the SO_REUSEPORT socket
> option which increased performance of nginx and had better balancing
> of connections across sockets of workers.
> Since Squid has the issue that load is not very well balanced between
> workers, I thought it is interesting to look at.

Thanks. This is something we could maybe use to reduce the amount of UDP
exchanges between workers and coordinator on startup. Since it prevents
the need for each worker to have the exact same FD socket ID for
http_port's. They woudl still have to inform the coordinator of those
IP:port being used anyhow.

But it will not help with the performance side of things during normal
operation since load != connection count.

I imagine that Nginx are seeing latency reduction due to no longer
needing a central worker that receives the connection then spawns a
whole new process to handle it. The behaviour sort of makes sense for a
web server (which Nginx is at heart still, a copy of Apache) spawning
CGI processes to handle each request. But kind of daft in these HTTP/1.1
multiplexed performance-centric days.


More information about the squid-dev mailing list