[squid-users] refresh_pattern and same objects

[Yuri Voinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 
This is only example. It is obvious we need investigate every case
separately and write/correct rules if it is needed.

Big mistake to assume that there is a magic set of rules that is
suitable for all occasions. Which allows to achieve a high hit ratio.
Obviously, it does not exist. Traffic is different in each of us. I just
want to say that we should not dogmatically assumed 30% good caching. As
I said, this gain is not worth the presence of excess server
infrastructure. Not counting the cost of its administration. But it is
worth some effort to improve the efficiency of caching. Otherwise it
makes no sense to use a caching proxy. There are a lot of decisions
without caching.

03.09.15 0:48, Amos Jeffries пишет:
> On 3/09/2015 3:04 a.m., Yuri Voinov wrote:
>>
>> 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.
>
> No arguments about that particular site. You found, what you found.
>
> But that is also what I keep saying to people, investigate each case and
> be sure about it first. The pattern you created from this one site was
> applied *everywhere* all at once. Nobody knows what its broken already,
> or about to.
>
> So best way is to create a pattern for the site and any others you find
> using the same software. Maybe you could sniff the Server headers or
> something to identify a common CMS system doing this and apply the
> pattern to its outputs. Lots of captures but still less than _everywhere_.
>
> Amos
> _______________________________________________
> 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
 
iQEcBAEBCAAGBQJV509EAAoJENNXIZxhPexGb9oIAJYFjbQWOKLb4ijbtz7Po5Dr
aASJ91Omb6SX57TsZfmvRVacMtwfAjpKEcxOv4f9kuTuCOFat/jigtpvlRpHjnLz
/YMis9qKgXz4BCYOoGm9Fdyl3dEd/SPmHttAM9UZJb4ym8dZ62E+L+WaZV9PIVfx
qY8bmFoD6w45sncH0XGHaOoeAMkxa4Rh8lx+1QQo3YcM0RoTExnR+AqbkWTsBioN
rcKFBVWTTejPRfqCASnD+EU0KsORPanQ0IiUl7Os8WEvcBn9RSd0tPKqnJ7BqhvL
VfYowhG00l/noWbQrOXTG+TuRtF8CK1xggHlDPy7PDDdOeTUiHjpCeWHjpeZEM0=
=lhGg
-----END PGP SIGNATURE-----