Forum Discussion
Michael_Harwoo1
Sep 25, 2015Nimbostratus
Only send connections to server2 if connection limit reached on server1
I have 4 HTTP web caching servers in a pool, and we want to try and increase the cache hit rate (likihood that it will have already cached the requested page) by focusing all connctions on one server...
Ed_Summers
Sep 25, 2015Nimbostratus
I am stepping outside my area of expertise and hope to learn from this discussion. My understanding of the goal of having caching servers in a pool was to allow balancing across the pool while using some method (such as destination-address persistence) to ensure that requests for a single object are always sent to the same caching server. I'm sure there are other/more granular ways to control which resource requests go to which caching servers.
Are you already employing some sort of logic to 'persist' requests for the same resource to the same caching server, and having problems with one cache server being 'overloaded'?
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