Forum Discussion

Sero_83363's avatar
Sero_83363
Icon for Nimbostratus rankNimbostratus
Nov 28, 2014

Basic web server LB http\https

Hi

 

This is a fairly basic, newbie question regarding best practice for a web server LB setup. We will be supporting http and https.

 

1) Which protocol profile should I use? All traffic is routed through the F5 and the F5 is behind a firewall (no SNAT\NAT). The clients will be on the internet and across the WAN. Fast Layer 4 or tcp-wan-optimized?

 

2) Should I be concered about the idle timeout default of 300 seconds? My assumption is that the web server and client will send http keep alives that will prevent the connection being idle over 300 seconds. But I am concerned that this very low value might causes issues.

 

Appreciate any guidance or pointers to documentation

 

Thanks in advance

 

application delivery
deployment
LTM
performance

1 Reply

Sort By
  • R_Marc's avatar
    R_Marc
    Icon for Nimbostratus rankNimbostratus
    Nov 28, 2014

    On 1, I would just stick to standard TCP, unless you have a specific requirement for the optimized profiles. It's trivial to switch between those optimized profiles, so you could just evaluate them, since this is a new setup. In my experience, those don't add much to a standard web app and the "fast" profiles can limit some capabilities. OneConnect does more to improve performance than anything I've evaluated, especially with https.

     

    On 2 300 seconds is a standard timeout setting. If you have some application that takes a long time to return a result (I've seen a lot of reporting applications that can be like that) you might need to increase it, but I would only do that on an as needed basis as you could impact performance of the entire unit if you have too many open connections.