APM Slow ISSUE

If you have enabled debugs during deployment stage, you should turn it off.

If you have enabled debugs during deployment stage, you should turn it off.

What sort of access methods are in use? Portal Access, Network Access, Application Tunnels, or LTM+APM mode?

Here are some things you can check:

1- With Network Access, you can choose how to SNAT (nat the client's source IP address). Make sure you're not using that if SMB access is being used. Some Windows Networking filers don't work well when several clients are accessing the same servers with the same source IP. Note that the appropriate SNAT settings are in the Network Access profile, not the Virtual Server. When not using SNAT, make sure you have your Lease Pool off in a different pool of IPs and that your internal routers will route traffic back to BIG-IP for the pool. Ref: http://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-network-access-11-4-0/2.html

2- You can use TLS (TCP) or DTLS (UDP) with Network Access. DTLS usually (but not always, depending on ISP conditions) has better performance. DTLS is a safe bet.

3- You can configure Optimized Applications for specific TCP ports (80, 443, etc). Optimized Applications uses a much more efficient transport (isession), and can utilize compression. Ref: http://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-network-access-config-11-1-0/3.html

4- As kunjan mentioned, you should check the log levels. Notice is the default log level for Access. Debug should not be used in production except for testing purposes, with special emphasis on Rewrite (Portal Access) and Secure Web Gateway (forward proxy). Ref: http://support.f5.com/kb/en-us/solutions/public/5000/500/sol5532.html

Try these things first. We usually find that complaints of Network Access slowness can be resolved with a combination of these configuration options.