Re: FreeBSD CPU Affinity

2017-08-17 Thread Willy Tarreau
On Wed, Aug 16, 2017 at 05:52:51PM +0200, Olivier Houchard wrote: > Willy, can you apply this ? > Of course, I forgot to mention it in the commit log, but this should probably > be backported to supported releases. Now done, thanks! willy

Re: FreeBSD CPU Affinity

2017-08-17 Thread Olivier Houchard
On Thu, Aug 17, 2017 at 04:27:55PM +0300, Dmitry Sivachenko wrote: > > > On 16 Aug 2017, at 18:32, Olivier Houchard wrote: > > > > > > > > I think I know what's going on. > > Can you try the attached patch ? > > > > Thanks ! > > > > Olivier > > <0001-MINOR-Fix-CPU-usage-on-FreeBSD.patch> >

Re: FreeBSD CPU Affinity

2017-08-17 Thread Dmitry Sivachenko
> On 16 Aug 2017, at 18:32, Olivier Houchard wrote: > > > > I think I know what's going on. > Can you try the attached patch ? > > Thanks ! > > Olivier > <0001-MINOR-Fix-CPU-usage-on-FreeBSD.patch> Also, it would be probably correct thing to check return code from cpuset_setaffinity() and

Re: FreeBSD CPU Affinity

2017-08-16 Thread Olivier Houchard
On Wed, Aug 16, 2017 at 11:43:30AM -0400, Mark Staudinger wrote: > On Wed, 16 Aug 2017 11:32:01 -0400, Olivier Houchard > wrote: > > > On Wed, Aug 16, 2017 at 11:28:52AM -0400, Mark Staudinger wrote: > > > On Wed, 16 Aug 2017 10:47:32 -0400, Dmitry Sivachenko > > > > > > wrote: > > > > > > > >

Re: FreeBSD CPU Affinity

2017-08-16 Thread Mark Staudinger
On Wed, 16 Aug 2017 11:32:01 -0400, Olivier Houchard wrote: On Wed, Aug 16, 2017 at 11:28:52AM -0400, Mark Staudinger wrote: On Wed, 16 Aug 2017 10:47:32 -0400, Dmitry Sivachenko wrote: > > > On 16 Aug 2017, at 17:40, Mark Staudinger > > wrote: > > > > On Wed, 16 Aug 2017 10:35:05 -0400

Re: FreeBSD CPU Affinity

2017-08-16 Thread Olivier Houchard
On Wed, Aug 16, 2017 at 11:28:52AM -0400, Mark Staudinger wrote: > On Wed, 16 Aug 2017 10:47:32 -0400, Dmitry Sivachenko > wrote: > > > > > > On 16 Aug 2017, at 17:40, Mark Staudinger > > > wrote: > > > > > > On Wed, 16 Aug 2017 10:35:05 -0400, Dmitry Sivachenko > > > wrote: > > > > > > > He

Re: FreeBSD CPU Affinity

2017-08-16 Thread Mark Staudinger
On Wed, 16 Aug 2017 10:47:32 -0400, Dmitry Sivachenko wrote: On 16 Aug 2017, at 17:40, Mark Staudinger wrote: On Wed, 16 Aug 2017 10:35:05 -0400, Dmitry Sivachenko wrote: Hello, are you installing haproxy form FreeBSD ports? I just tried your configuration and it works as you ex

Re: FreeBSD CPU Affinity

2017-08-16 Thread Mark Staudinger
On Wed, 16 Aug 2017 10:47:32 -0400, Dmitry Sivachenko wrote: Strange. I am testing on FreeBSD-10-stable though. May be you add return code check for cpuset_setaffinity() and log possible error? That might be relevant. My FreeBSD-10.0 test server does also exhibit the expected behavior

Re: FreeBSD CPU Affinity

2017-08-16 Thread Dmitry Sivachenko
> On 16 Aug 2017, at 17:40, Mark Staudinger wrote: > > On Wed, 16 Aug 2017 10:35:05 -0400, Dmitry Sivachenko > wrote: > >> Hello, >> >> are you installing haproxy form FreeBSD ports? >> >> I just tried your configuration and it works as you expect. >> >> If you are building haproxy by hand

Re: FreeBSD CPU Affinity

2017-08-16 Thread Mark Staudinger
On Wed, 16 Aug 2017 10:35:05 -0400, Dmitry Sivachenko wrote: Hello, are you installing haproxy form FreeBSD ports? I just tried your configuration and it works as you expect. If you are building haproxy by hand, add USE_CPU_AFFINITY=1 parameter to make manually. FreeBSD port do that for

Re: FreeBSD CPU Affinity

2017-08-16 Thread Dmitry Sivachenko
> On 16 Aug 2017, at 17:24, Mark Staudinger wrote: > > Hi Folks, > > Running HAProxy-1.7.8 on FreeBSD-11.0. Working with nbproc=2 to separate > HTTP and HTTPS portions of the config. Hello, are you installing haproxy form FreeBSD ports? I just tried your configuration and it works as you

FreeBSD CPU Affinity

2017-08-16 Thread Mark Staudinger
Hi Folks, Running HAProxy-1.7.8 on FreeBSD-11.0. Working with nbproc=2 to separate HTTP and HTTPS portions of the config. Given the following config: global nbproc 2 cpu-map 1 2-8 cpu-map 2 7-14 After starting HAProxy, there are, as expected, two processes running.