TCP profile - client and server

The performance of your web server doesn't matter necessarily. The conditions of the LAN are what matter. So, if you are on a local segment, use the TCP-Lan-optimized for the server-side and the WAN-optimized for the client-side.

 

If you have a high performance server in Hong Kong and your BIG-IP in London and you're accessing it over an internet link, then you'd want to use the wan-optimized in that case.

 

Using FastL4 and not taking advantage of the dual tcp stacks just means that your "High Powered Server" is going to have to use the least common TCP options that each client supports individually and will need to negotiate different tcp options for each client. So, if some clients are coming in with windows 2000 on a dial-up connection, then your server will spend resources lowering window sizes, dropping packets and being inefficient.

 

With the LTM full proxy in line, your server will always get optimal tcp options from a tcp-wan-optimized profile on the server-side of the BIG-IP LTM and the clients each get handled as best they can with the wan-optimized.