Hi Eliezer, thank you for your answer The origin servers are the same in 2.6 and in 3.3 (in both cases Squid connect to the same origin remote servers) and the squid.conf is exactly the same except in the very first lines (since acl manager proto cache_object , etc. are obsolote). The vast majority of the misses are TCP_MISS/200. I checked several times the last 200 requests to the homepage of our site (the min/max age is 1 minute -but also tried with a few more minutes-) in the access.log file and these were the results: Squid 2.6: 1st check: 5 misses of 200 requests 2nd check: 0 misses of 200 requests 3rd check: 2 misses of 200 requests Squid 3.3: 1st check: 59 misses of 200 requests 2nd check: 32 misses of 200 requests 3rd check: 108 misses of 200 requests *Nothing was touched between each check, just a pause of a few seconds or minutes. I was think that maybe I should --enable-http-violations in Squid3.3 to get use of override-expire ignore-reload but I think that it is already enabled by default since negative_ttl is working properly and requires --enable-http-violations . Indeed I reduced some misses by using negative_ttl on squid.conf because Squid3.3 was doing misses with 404 requests while Squid2.6 was doing hits without the need of setting that directive. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Why-are-we-getting-bad-percentage-of-hits-in-Squid3-3-compared-with-Squid2-6-tp4662949p4662956.html Sent from the Squid - Users mailing list archive at Nabble.com.
