外国人写的一篇关于F5 oneconnect的理解.docVIP

外国人写的一篇关于oneconnect的理解 F5 OneConnect F5 has a trademark feature called OneConnect that leverages?HTTP 1.1 Keepalive.?In this article, I will try to explain the functionality of OneConnect, underlying technology and its usage requirements. There are 2 main reasons that I have utilized OneConnect profile: Efficient reuse of server side connections (F5-Servers) L7 Content Switching i.e., when the F5 is configured to make load balancing or persistence decision based on information available in L5 to L7. Efficient TCP Connection Reuse: Every time a new connection is set up on the server, the server has to allocate resources. What Resources: Resources like State/buffer memory at the Kernel level memory per thread as each connection consumes web server threads. There is also an impact on the CPU of the server as the server needs to keep track of the web threads and connections. The consumption of resources outlined earlier won’t affect a small to medium scale load balanced web-server infrastructure. However, as the traffic flow increases, the servers can take quite a big hit. At this point, the option would be to add more servers which can increase your CapEx and of course, OpEx?will rise for administrative reasons. OneConnect, if used properly will provide you with a method to efficiently utilize the existing infrastructure without the requirement for adding more physical servers. ?This is done by leveraging existing server side connections using HTTP 1.1 Keepalive. Lets say, client IP is initiating a connection to the VIP 0 which then gets load balanced to the server 0. Within the TCP connection, the client will utilize multiple HTTP Requests to obtain the right content from the server (HTTP 1.1 Keepalive). After the transaction has been completed, the client closes the client side connection (Client – F5). However, the F5 retains the server side connection (F5-Server). If a new client () initiates a connection within a certain timeout interval, the F5 will re-use the