Forum Discussion
brad_11440
Nimbostratus
NimbostratusFastL4 vs Optimized TCP Profiles
We run active/standby 6400 (platform D63a) LTM's for our production applications. They are accessed via clients on a private network with an average latency around 80ms. Nearly all of our virtual se...
- Maybe it's about the right time to have you post your VIP config from the bigip.conf. It's possible you have other settings applied to the VIP which conflict with a FastL4 profile??? Also it might be helpful to paste the values of the TCP profile you have applied.
Regarding the window size...the behavior you see was bothering me for a long time until it finally clicked in my brain. Yes, the TCP window size always starts at 4380. The trick is to understand whether the LTM is sending or receiving data. When the LTM is sending data, as in this case, there is no need for the LTM to increase its receive window - which is the parameter you refer to in the trace.
When the LTM is receiving large amounts of data and you do a trace, you'll see that the LTM receive window starts out at 4380, and quickly increases to the value of the Receive Window as specified in the TCP profile that is applied.
The LTM is smart - it starts out with a small window size so it does not need to allocate more memory than necessary for the TCP connection. If it needs to adjust the receive window (when it is receiving data), you'll see it go up.
brad_11440Nimbostratus
NimbostratusWe are not pushing the box at all right now. CPU and memory utilization are relatively low. I assumed FastL4 would be best since it processes the traffic in hardware. Same reasons switches operate faster than routers (hey, I am a network engineer!). When you say "if you want to optimize http in any way", do you mean for those VIP's where FastL4 is not an option ? Most of our VIPs will be able to use FastL4 but for those that can not we will definitely move to LAN Optimized on both sides. Thanks again. I really hope this makes a difference.