Primedius
asked on
Squid Connection Pools
Hey Guys,
I am trying to ease the network strain on a single server instance while we work to make our app multi-home/cluster across multiple server instances. One consultant is suggesting an F5 BIG-IP with the Local Traffic Manager (LTM) and use the OnceConnect feature to mux down TCP connections ( TCP multiplexing). One of our internal guys is suggesting Squid's connection pools will do the same thing. Is that true? Does it also do TCP multiplexing?
I am trying to ease the network strain on a single server instance while we work to make our app multi-home/cluster across multiple server instances. One consultant is suggesting an F5 BIG-IP with the Local Traffic Manager (LTM) and use the OnceConnect feature to mux down TCP connections ( TCP multiplexing). One of our internal guys is suggesting Squid's connection pools will do the same thing. Is that true? Does it also do TCP multiplexing?
Yes, squid does connection decoupling/pooling as well as F5 oneconnect profile. cache_peer option has some control over connection pooling. But this only works over HTTP protocol (i e layer7). Squid does not support plain TCP, F5 will not do pooling if it has no L7 protocol knowledge on top of TCP, because how would it know when is the end of the message and at which point it can do multiplexing?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What is TCP multiplexing? Can you show me RFC standard? I personally never heard of such extension. Higher level protocols like HTTP/2 or SSH does that.
Can you use netflow or snmp to cpunt connections from the net and connections to the backend?
basically counting from the public side
~100 - standard apache
~1000 worker pache
~10000 event apache
~100000 nginx/varnish/squid