NimbostratusAs the BIG-IP is a full proxy there's actually two tcp profiles to consider - server facing and client facing. In general, server side gets a LAN (low latency & no congestion) profile and client side would get the WAN profile (higher latency and a better chance of congestion). To start with, I would consider building two virtual servers; one for internal connections LAN/LAN and one for external connections (LAN/WAN) for server/client connectivity.
If you haven't already, read everything on DevCentral by Martin Duke. In particular:
https://devcentral.f5.com/articles/stop-using-the-base-tcp-profile
AND
https://devcentral.f5.com/articles/tuning-the-tcp-profile-part-one
Of course, tuning the BIG-IP is only part of the solution, tuning the server (pool members) and potentially your client systems can have dramatic results.
