On Thu, Feb 17, 2022 at 07:57:30AM +0100, Vincent Bernat wrote:
> ? 16 February 2022 22:15 +01, Willy Tarreau:
>
> > That's exactly the sense behind the word "maybe" above, to open the
> > discussion :-) Those with large buffers can definitely see a
> > difference. I've seen configs with WAF
❦ 16 February 2022 22:15 +01, Willy Tarreau:
> That's exactly the sense behind the word "maybe" above, to open the
> discussion :-) Those with large buffers can definitely see a
> difference. I've seen configs with WAF analysis using 1MB buffers,
> and there the extra CPU usage will be
On Wed, Feb 16, 2022 at 09:57:45PM +0100, Christian Ruppert wrote:
> On 2022-02-16 19:08, Vincent Bernat wrote:
> > ? 16 February 2022 16:27 +01, Willy Tarreau:
> >
> > > Maybe that would even be a nice improvement for distros to provide
> > > these
> > > by default starting with 2.6 or maybe
Hi Vincent,
On Wed, Feb 16, 2022 at 07:08:38PM +0100, Vincent Bernat wrote:
> ? 16 February 2022 16:27 +01, Willy Tarreau:
>
> > Maybe that would even be a nice improvement for distros to provide these
> > by default starting with 2.6 or maybe even 2.5.
>
> Why not enabling them directly on
❦ 16 February 2022 16:27 +01, Willy Tarreau:
> Maybe that would even be a nice improvement for distros to provide these
> by default starting with 2.6 or maybe even 2.5.
Why not enabling them directly on your side then? Are there some numbers
on the performance impact of these options? I am a
Hi,
HAProxy 2.4.13 was released on 2022/02/16. It added 28 new commits
after version 2.4.12.
No need to read this if you already read the 2.5.2 announcement :-)
This is essentially the same as what changed from 2.5.1 to 2.5.2, except
master and httpclient, so I'm copy-pasting here the relevant
Hi,
HAProxy 2.5.2 was released on 2022/02/16. It added 44 new commits
after version 2.5.1.
This version addresses a few long-term bugs that have been keeping us
quite busy for far too long, but ultimately it's satisfying to know that
these ones are gone and that they won't be casting a doubt
Hi all,
I am running HAProxy 2.3.14 in a Kubernetes cluster managed by the
haproxy-ingress ingress controller:
https://github.com/jcmoraisjr/haproxy-ingress
There are sporadic connection resets and by capturing traffic I could identify
the proxy to be the origin. The author of haproxy-ingress
8 matches
Mail list logo
