On 15/07/17 11:28, Ivan Larionov wrote:
Ok, mystery solved.
Patch "HTTP: do not allow Proxy-Connection to override Connection
header" changes the behavior. And we indeed send from our clients:
Connection: close
Proxy-Connection: Keep-Alive
Ah. Yes that would lead to trouble.
If you have a
Ok, mystery solved.
Patch "HTTP: do not allow Proxy-Connection to override Connection header"
changes the behavior. And we indeed send from our clients:
Connection: close
Proxy-Connection: Keep-Alive
On Sat, Jul 8, 2017 at 9:51 AM, Ivan Larionov wrote:
> RPS didn't change. Throughput didn't c
RPS didn't change. Throughput didn't change. Our prod load is 200-700 RPS
per server (changes during the day) and my load test load was constant 470
RPS.
Clients didn't change. Doesn't matter if they use HTTP 1.1 or 1.0, because
the only thing which changed is squid version. And as I figured out,
On 08/07/17 02:06, Ivan Larionov wrote:
Thank you for the fast reply.
On Jul 7, 2017, at 01:10, Amos Jeffries wrote:
On 07/07/17 13:55, Ivan Larionov wrote:
>>>
However I assumed that this is a bug and that I can find older version which
worked fine. I started testing from 3.1.x all the w
> -Original Message-
> From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On
> Behalf Of Ivan Larionov
> Sent: Friday, July 7, 2017 17:07
> To: Amos Jeffries
> Cc: squid-users@lists.squid-cache.org
> Subject: Re: [squid-users] Huge amount of time_wait conn
On Behalf
Of Ivan Larionov
Sent: Friday, July 7, 2017 17:07
To: Amos Jeffries
Cc: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Huge amount of time_wait connections after upgrade
from v2 to v3
Thank you for the fast reply.
> On Jul 7, 2017, at 01:10, Amos Jeffries wrote:
>
Thank you for the fast reply.
> On Jul 7, 2017, at 01:10, Amos Jeffries wrote:
>
>> On 07/07/17 13:55, Ivan Larionov wrote:
>> Hi. Sorry that I'm answering to the old thread. I was on vacation and didn't
>> have a chance to test the proposed solution.
>> Dieter, yes, I'm on the old CentOS 6 bas
On 07/07/17 13:55, Ivan Larionov wrote:
Hi. Sorry that I'm answering to the old thread. I was on vacation and
didn't have a chance to test the proposed solution.
Dieter, yes, I'm on the old CentOS 6 based OS (Amazon Linux) but with a
new kernel 4.9.27.
Amos, thank you for the suggestions abo
Hi. Sorry that I'm answering to the old thread. I was on vacation and
didn't have a chance to test the proposed solution.
Dieter, yes, I'm on the old CentOS 6 based OS (Amazon Linux) but with a new
kernel 4.9.27.
Amos, thank you for the suggestions about configure flags and squid config
options,
On 07/06/17 12:13, Ivan Larionov wrote:
Hi!
We recently updated from squid v2 to v3 and now see huge increase in
connections in TIME_WAIT state on our squid servers (verified that
this is clients connections).
The biggest change between 2.7 and 3.5 in this area is that 2.7 was
HTTP/1.0 whic
Hi Ivan,
On Tue, Jun 06, Ivan Larionov wrote:
> We recently updated from squid v2 to v3 and now see huge increase in
> connections in TIME_WAIT state on our squid servers (verified that this is
> clients connections).
I can confirm that since 3.5.22 to our ICAP scanners.
with 3.5.21 we had no pr
Hi!
We recently updated from squid v2 to v3 and now see huge increase in
connections in TIME_WAIT state on our squid servers (verified that this is
clients connections).
See versions and amount of such connections under the same load with the
same configs (except some incompatible stuff):
squid
12 matches
Mail list logo
