My total hit ratio decreased in ~2 times from 40% to 20% (it could be cold
cache but it lasted at this level for a day without sign of improvement).
I'll retry tests with making sure there're no Vary header and will also try
1 worker with shared cache tomorrow. But even if it is this bug looks
My disks are fast (SSD) so I didn't see performance issues but it doesn't
change the fact that memory hit ratio decreased in more than 10 times. And
with both rock and shared memory cache enabled most of the files were saved
into disk cache and not into memory cache and most of the hits were disk
On 01/15/2018 02:12 PM, Brian J. Murrell wrote:
> On Mon, 2018-01-15 at 13:48 -0700, Alex Rousskov wrote:
>>
>> both transparent and forward/explicit proxies have approximately the same
>> support for HTTPS. In other words, if you find a forward/explicit
>> proxy useful for HTTPS, then a
On Mon, 2018-01-15 at 13:48 -0700, Alex Rousskov wrote:
>
> That statement does not compute in the current context: A transparent
> proxy has many disadvantages over a forward/explicit proxy,
Sure. But it has advantages also.
> but both
> transparent and forward/explicit proxies have
On 01/15/2018 11:56 AM, Snyder, Brian wrote:
> I have not found an issue the hardware.
To avoid misunderstanding, I did not imply that there are
hardware-related issues. My question was about bottlenecks (i.e.,
resources that are being overused, including hardware resources like CPU
or RAM and
On 01/15/2018 12:31 PM, Brian J. Murrell wrote:
> On Mon, 2018-01-15 at 12:26 -0700, Alex Rousskov wrote:
>> What about the transparent proxy part?
> I already have that, but that is becoming more or less useless in the
> everything-https world we are heading towards since you can't
>
On Mon, 2018-01-15 at 12:26 -0700, Alex Rousskov wrote:
>
> What about the transparent proxy part?
I already have that, but that is becoming more or less useless in the
everything-https world we are heading towards since you can't
transparently proxy https. AFAIU.
> if Squid closed a CONNECT
On 01/15/2018 11:32 AM, Brian J. Murrell wrote:
> On Mon, 2018-01-15 at 10:56 -0700, Alex Rousskov wrote:
>> On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
>>> On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
In that case, there are two HTTP connections in play:
1. An HTTP
On 01/15/2018 08:22 AM, Amos Jeffries wrote:
> AIUI, SMP-mode rock operates as a fully separate process (a "Disker"
> kid) which delivers its results as objects already in shared memory
> to the worker process.
Yes, disk hits are delivered to workers via shared memory, but...
> There should
Thank you for your reply. I have not found an issue the hardware. Atop shows
everything in normal ranges. I do know the squid is about 50% faster with our
filter set up as a parent vs routing through it normally. Not sure why that
would be. However, when I set it up as a parent I notice quite a
On 16/01/18 07:32, Brian J. Murrell wrote:
On Mon, 2018-01-15 at 10:56 -0700, Alex Rousskov wrote:
On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
In that case, there are two HTTP connections in play:
1. An HTTP connection from the
On 16/01/18 05:26, Bruce R wrote:
Is it possible to configure Squid to log the details of the PROXY
protocol when using it? We're running Squid 3.5.20 in AWS behind a TCP
load balancer, which supports forwarding the PROXY protocol header. I'd
like to be able to include the client IP as
On Mon, 2018-01-15 at 10:56 -0700, Alex Rousskov wrote:
> On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
> > On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
> > > In that case, there are two HTTP connections in play:
> > >
> > > 1. An HTTP connection from the client to the origin
> >
On 01/14/2018 10:53 PM, Ivan Larionov wrote:
> After migrating squid from non-SMP/aufs to SMP/rock memory cache hit
> ratio dropped significantly. Like from 50-100% to 1-5%.
This could be a side effect of not supporting Vary caching in shared
memory:
On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
> On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
>> In that case, there are two HTTP connections in play:
>>
>> 1. An HTTP connection from the client to the origin server.
> By this do you mean to say there is a connection from the
On Mon, 2018-01-15 at 16:06 +, Rafael Akchurin wrote:
> Hello Brian,
Hi,
> *but* the same 200 of tabs loads just fine from FF and the same Squid
> on the same machine at the same time - so might be a Chrome
> issue/architecture?
Interesting. I'm not sure how I would do it, but it would be
Is it possible to configure Squid to log the details of the PROXY
protocol when using it? We're running Squid 3.5.20 in AWS behind a TCP
load balancer, which supports forwarding the PROXY protocol header. I'd
like to be able to include the client IP as provided in the PROXY
protocol header,
Hello Brian,
Sorry not to flame it all out further - but I see the same annoying "waiting
for proxy tunnel" in Chrome through SSL bumping AD integrated explicit Squid.
*but* the same 200 of tabs loads just fine from FF and the same Squid on the
same machine at the same time - so might be a
On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
> In that case, there are two HTTP
> connections
> in play:
>
> 1. An HTTP connection from the client to the origin server.
By this do you mean to say there is a connection from the client,
through the proxy server to the origin server?
On 15/01/18 18:53, Ivan Larionov wrote:
Hello!
After migrating squid from non-SMP/aufs to SMP/rock memory cache hit
ratio dropped significantly. Like from 50-100% to 1-5%. And disk cache
hit ratio went up from 15-50% to stable 60-65%. From the brief log file
check it looks like in SMP/rock
20 matches
Mail list logo
