Hoi Willy!
What a detailed and fruitful response, as always
On 27/3/19 10:56 μ.μ., Willy Tarreau wrote:
> Hi Pavlos!
>
> On Wed, Mar 27, 2019 at 09:57:32PM +0100, Pavlos Parissis wrote:
>> Have you considered enabling SO_INCOMING_CPU socket option in
>> order to increase data locality and CPU ca
Hi Pavlos!
On Wed, Mar 27, 2019 at 09:57:32PM +0100, Pavlos Parissis wrote:
> Have you considered enabling SO_INCOMING_CPU socket option in
> order to increase data locality and CPU cache hits?
No, really for our use case I'm not convinced at all by it, I'm only
seeing risks of making things much
On 26/3/19 6:24 π.μ., Willy Tarreau wrote:
> Hi,
>
> HAProxy 2.0-dev2 was released on 2019/03/26. It added 176 new commits
> after version 2.0-dev1.
>
> This version starts more important changes. One of the most visible
> ones is that haproxy will now automatically start with threads enabled
> i
Hi,
HAProxy 2.0-dev2 was released on 2019/03/26. It added 176 new commits
after version 2.0-dev1.
This version starts more important changes. One of the most visible
ones is that haproxy will now automatically start with threads enabled
if neither "nbthread" nor "nbproc" is configured. It will ch
4 matches
Mail list logo