Forum Discussion
snickerbooze_13
Oct 26, 2011Nimbostratus
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 report...
snickerbooze_13
Nov 22, 2011Nimbostratus
Okay, true or false:
Scenario 1)
windows 2003 defualt is 64240. Big IP recieve window defaut is 32768 for TCP profile.
Question 1)
is this telling me that the largest window that is going to be advertised is 32768 to the client even though the windows default 64240? Would that be a bottle neck of sorts?
Scenario 2)
proxy buffer high is default 16384. This means big ip recieve window closes at half the window size.
Question 2)
IS this recieve window closed same as zero window in some way?
So far, all indication are that the settings on my f5 are bottle necking my server by conflicting settings. I realize this is not a knock on f5, rather my configurtaion setup not optimized. I am trying to ascetain reason behind the settings for big ip optimized profiles and how it could help performance in my case.
I tried to use wire shark to see the window size but it is inconclusivve to me. I see window size of 64k from iis server to big ip. From big ip to server is see window in the range of 8k maybe. I am un able to determine the meaning of that at this point. If someone can help a guy out that'd be great
thanks,
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects