On 30/10/2013 2:51 a.m., Ayham Abou Afach wrote:
Hi
i have the folloing problem after moving from squid 3.1 to ( 3.2 or 3.3
) with same config
bandwidth saving decreases to about 50%
what is the deffirance between versions related to caching behaviour ???
any one has a solution to this problem...
Regards
The big caching related changes:
* 3.2 version is now HTTP/1.1 - with extended cacheability and
revalidation behaviour.
- In some cases HTTP/1.0-based savings calculation can show a decrease
even as total bandwidth is reduced.
- More cacheable content (in HTTP/1.1 almost anything is cacheable)
can mean more spare HIT rate.
- avg store object age, size, near-HIT ratio also need to be
considered more important for HTTP/1.1
- NP: Several of the refresh_pattern ignore-* and override-* options
cause *reduction* in HTTP/1.1 compliant caches.
* 3.2 version is validating intercepted traffic safety.
- Unsafe traffic will not be cached.
* 3.2 cache size calculations have been updated.
- Uncovering a bug where the maximum_object_size directive must be
placed above the cache_dir for it to have any effect raising the object
size limit on those cache_dir.
Amos
