-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I confirm: 3.5.10 has normal cache-hits rate. Against 4.0.1. For the
same sites.
Something broken in 4.x.
27.10.15 1:37, Amos Jeffries пишет:
> On 27/10/2015 6:22 a.m., Yuri Voinov wrote:
>>
>> Ah, ok:
>>
>> We see in redbot.org this info in
I understand perfectly. However - I changed version of the proxy and
everywhere at the same time changed the headlines? Now I will return the
version 3.4 and everything will be as it was. I already did.
That's why I ask the question - what has changed so much that the same
configuration I
Hey Yuri,
What have you tried until now to understand the situation of the issue?
From your basic question I was sure that you ran some tests on some
well defined objects.
To asses the state of squid you would need some static objects and some
changing objects.
You would also be required to
On 27/10/2015 6:22 a.m., Yuri Voinov wrote:
>
> Ah, ok:
>
> We see in redbot.org this info in server response:
>
> Cache-Control: no-cache
>
It also says "this content was negotiated but does not have an
appropriate Vary header". Which is marked as a protocol error.
And has a status code of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
27.10.15 1:37, Amos Jeffries пишет:
> On 27/10/2015 6:22 a.m., Yuri Voinov wrote:
>>
>> Ah, ok:
>>
>> We see in redbot.org this info in server response:
>>
>> Cache-Control: no-cache
>>
>
> It also says "this content was negotiated but does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Here is one day Squid 4 working statistics (by Calamaris):
http://i.imgur.com/XeYRWbY.png
It's about nothing. Squid 3 in bad days easy achieves 35%
26.10.15 23:34, Alex Rousskov пишет:
> On 10/26/2015 11:19 AM, Yuri Voinov wrote:
>
>> 4.0.1
On 10/26/2015 11:19 AM, Yuri Voinov wrote:
> 4.0.1 has more than 4 times
> bigger mem_cache, 1 Gb. 1st example 3.5.10 has only 256 Mbytes. This is
> the reason of miss??
Please see my previous email if you want to improve your chances of
getting a correct answer to that and other related
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This should be understood as "Life Saving handiwork of drowning." Or "We
change something, but you sort it out, how to fix it, it's the Open
Source, baby";)
So, finally, there is no answer.
PS. If developers do not know - the more we do not know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The answer is simple.
Look ath this row from 3.5.10 access.log:
1445879345.827 48 127.0.0.1 TCP_MEM_HIT/200 24425 GET
https://upload.wikimedia.org/wikipedia/commons/thumb/8/8c/Teller-Ulam_device.png/200px-Teller-Ulam_device.png
- HIER_NONE/-
On 10/26/2015 04:41 AM, Yuri Voinov wrote:
> what has changed so much that the same
> configuration I get 10 times smaller cache hit.
You are asking a good question. I do not think anybody knows the exact
answer -- too many things have changed in general to either identify the
changes that have
I cannot speak for the Squid project and you may ask the squid-dev more
about it and also see the release notes about it.
What I can is that the phrase "it's not a bug, it's a feature" can work
the other way around "it's not a feature, it's a bug" and as you have
mentioned "it worked yesterday"
On 26/10/2015 9:53 a.m., Yuri Voinov wrote:
>
> I can not understand why so much dropped for caching of https.
I dont understand what you mean by that.
You started caching HTTPS and ratio dropped?
HTTPS is less than 30% of total traffic. But;
* has a higher proportion of Cache-Control:
On 26/10/2015 8:29 a.m., Yuri Voinov wrote:
>
> In a nutshell - I need no possible explanation. I want to know - it's a
> bug or so conceived?
Well, I don't think it is what you think.
For starters ignore-no-cache was removed back in 3.2, so your 3.4
version working okay shows that its not that
On 25/10/2015 21:28, Yuri Voinov wrote:
It's not about that. It's about the fact that, with exactly the same
parameters caching and maintaining the cache at the same URL, which I
used to get 85% cache hit, I am now, with a SQUID 4, I get 0%. That's all.
OK then, if it's that important for you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I can not understand why so much dropped for caching of https. This is
very critical in the modern conditions, for obvious reasons. In older
versions of the same for this to work. And it does not have the
slightest desire to write or use a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi gents,
Pay attention to whether someone from the test SQUID 4 as extremely low
of cache hits from the new version? Particularly with respect to sites
HTTPS directive "no cache"? After replacing the Squid 3.4 to 4 squid
cache hit collapsed from
Hey Yuri,
I am not sure if you think that Squid version 4 with extreme low hit
ratio is bad or not but I can understand your sight about things.
Usually I am redirecting to this page:
http://wiki.squid-cache.org/Features/StoreID/CollisionRisks#Several_real_world_examples
But this time I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In a nutshell - I need no possible explanation. I want to know - it's a
bug or so conceived?
26.10.15 1:17, Eliezer Croitoru пишет:
> Hey Yuri,
>
> I am not sure if you think that Squid version 4 with extreme low hit
ratio is bad or not but I can
18 matches
Mail list logo
