12-21-2010 01:15 PM
Digging through the forum, I found a few references about HTTP acceleration and that for the most part, it should be turned off...
Is this still true? I'm seeing peformance issues inside our network, running 5.7.5.
Solved! Go to Solution.
12-21-2010 01:49 PM
Here is a quote from 184.108.40.206 release notes on page 6.
When HTTP acceleration is enabled on a WX or WXC device with WXOS 5.7 (or
later), HTTP traffic is accelerated only for remote WX and WXC devices that have
WXOS 5.6.4 (or later).
HTTP acceleration in WXOS is designed to optimize traffic within an enterprise
network (intranet). While it is possible to configure this feature to optimize all HTTP
traffic, including to and from the internet, it is not a supported configuration.
Bottom line, HTTP acceleration is supported for Intranet traffic not for Internet traffic.
If you are trying to accelerate internet traffic and it is an absolute MUST for you to do that then here are certain recommendations that I always tell my customers;
1- Try to identify at least 30-40% of webservers and assign them a separate application definition and put them under HTTP traffic class and only enable HTTP acceleration for those apps only. This will help isolate most of uncessary traffic.
2- Keep an eye on the cache objects at all time and if possible clear the cache when it is about to reach the maximam number of 25600 objects. You can use the command "she oyo cacheShow" to see how many objects are there in the disk at any given time.
3- Disable the HTTP application acceleration for the rest of the internet traffic except the defined HTTP apps.
What I have seen in recent times is that when you enable HTTP acceleration globally for INTERNET traffic, it works fine for only a few days and then when the cache reaches the limit, it gets into a certain state where it runs out of system resources and then it slows down every other application as well. That is why this product was never designed to accelerate INTERNET HTTP traffic.
Let me know if that helps.
12-21-2010 01:56 PM
That makes a lot of sense, and explains why one of my boxes started throwing errors about http cache object collisions.
I guess I assumed that the algorithm figured out what was "internal" based on the compression subnets or default decompressors...
Thanks for your help!
12-21-2010 02:08 PM
Here are some of the typical errors you might be seeing in the logs;
I39 Trans 0x55372dc0 - HTTP object key collision: ret = 26,URI=en.wikipedia.orghttp://en.wikipedia.org/ski
I50 openRead-4024: URI length mismatch file=75 span=60 URI=www.tabonline.com.auhttp://www.tabonline.com.au/js
I39 writeHeadersToCache (trans=0x10cb5bc8): Fail to create the file 220.127.116.11/4k.html - err=OC_OUT_OF_RESOURCE