[squid-users] refresh_pattern and same objects

[Yuri Voinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 
Here is another case with the same image:

http://i.imgur.com/qM52aPQ.png

The same, right?

So, I proposed to leave thousands of copies of the same image, even
within a single user session, just because someone is afraid once again
to cache? And I know that the site in question, works perfectly and 100%
functional?

Don't think so.

02.09.15 16:23, Eliezer Croitoru пишет:
> On 02/09/2015 13:00, Yuri Voinov wrote:
>>
>> I'm getting a very high hit ratio in my cache.And I do not intend to
>> lower its with myself. Enough and that on the opposite side of the
>> thousands of webmasters counteract caching their content on its own
>> grounds. Beginning from YouTube.
>
> Well, Most sane server side caches do allow and work with a 304
validation and in many cases it's good.
> Notice that I have not seen an access.log analyzer that counts
re-validation successfully until now.
> I do not know what the situation of your bandwidth usage or needs but
there is a term which called "over caching" and it depends on the
environment.
> If you see that the cache is working for you with higher numbers then
30% consider that your cache maybe is caching more then the standard cache.
> I am pretty sure that a domain analysis can find the more accurate
refresh_patterns that can leave you with high cache hit ratio and still
make the cache less vulnerable to config mistakes.
>
> Maybe clients didn't complained until now but it doesn't states that
they do not have any issues. It's just that they didn't got to you yet.
> If you are using 3.4.X and up you are in a better place then in 3.2.X
and older version so squid should be safe enough for a very ambitious
config file.
>
> All The Bests,
> Eliezer
>
> * Thanks for sharing the refresh_patterns discussion with others
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQEcBAEBCAAGBQJV5xAFAAoJENNXIZxhPexGZlcIALdhOQhin8L2f72TAgMg60dx
e2rBs51K+utkbkBNO57kXgoi4w2QjqG4GhC1Vt8t1P/asABxo1GBL59TKbGEEuBU
rn50bOqm1sZCUK2jlc/MqrpNTpc+Zc9rBIFhcmhJ2GOU8oqN0xc0Itzv9ouJMBfT
O32Ohdual/vA30CRiDY2MgrvETekod5EBlOrHOYm52QTbI5d3Ji267WWtgEae4we
ams+YdmvkGfi/tDQLnpzcFXrFyIAGRCCakpAvTB3GkXwi7x3q5ogw64czC3f7IIE
F/NVlqq93WskHei6LflC7IG+H6hkUNM4IPuIGfkBV0ASHw54MOWRvaC507ZsTfo=
=aebz
-----END PGP SIGNATURE-----