IIS 6.0 seems slow behind BIG-IP
Short story:
Accessing site directly is faster than accessing through BIG-IP.
Long story:
I have been working through several issues with some success. The server is for reporting so some of the requests exceed 5 minutes. That was my first problem.
I was using the base tcp profile, but figured out that the connection was timing out when the connection was reset after 300 seconds. I created a new TCP profile with increase to 600 seconds. Problem appears to be resolved. However, this got me thinking....
The particular script used for testing takes just over 4 minutes when accessing directly. When i access through BIG-IP the request takes nearly 9 minutes. This is perplexing as it doesn't seem like what would be considered expected behavior.
So, the question is how big of a problem do i have. How many requests actually take longer than 5 minutes and out of those requests that do take longer than 5 minutes, how much of it is because it is slower because of BIG-IP?
With that said, it would appear that the profile setting is in need of some tuning. I notice there are other profile with the name of tcp-wan-optimized and such wich has higher threasholds in what appear to be the relevant areas.
My question is weather i am looking in the right place or not? I do not have access to the LB or i would check myself. I can request changes to be made, but cannot make requests one right after the other in a brute force approach.
Here is my setup:
browser -> BIG-IP ver 10 -> stand alone IIS server -> page_with_5_minute_query
thanks in advance, any help is appreciated.