On Fri, Apr 20, 2018 at 08:59:32PM +0300, Slawa Olhovchenkov wrote:
> Ok, I am got respons from thread 3 and thread 7.
And never the other ones ? That's kind of strange!
> Can I mean this threads mapped to CPU 3 and 7?
No, this is totally unrelated, unless of course you're using cpu-map to
map t
On Fri, Apr 20, 2018 at 08:32:28PM +0300, Slawa Olhovchenkov wrote:
> > > Can I got per-thread stats like connections count, bytes transfered?
> >
> > Not by default, as such information are per-socket, per-frontend etc.
> > However, by having on listening socket per thread, and "option socket-sta
On Fri, Apr 20, 2018 at 07:22:59PM +0200, Willy Tarreau wrote:
> On Fri, Apr 20, 2018 at 07:23:37PM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Apr 20, 2018 at 05:33:34PM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Fri, Apr 20, 2018 at 04:23:00PM +0200, Willy Tarreau wrote:
> > >
> > > > > >
On Fri, Apr 20, 2018 at 07:22:59PM +0200, Willy Tarreau wrote:
> On Fri, Apr 20, 2018 at 07:23:37PM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Apr 20, 2018 at 05:33:34PM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Fri, Apr 20, 2018 at 04:23:00PM +0200, Willy Tarreau wrote:
> > >
> > > > > >
On Fri, Apr 20, 2018 at 07:23:37PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Apr 20, 2018 at 05:33:34PM +0300, Slawa Olhovchenkov wrote:
>
> > On Fri, Apr 20, 2018 at 04:23:00PM +0200, Willy Tarreau wrote:
> >
> > > > > Thus for you it's better to stick to a single listener, and if you
> > > >
On Fri, Apr 20, 2018 at 05:33:34PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Apr 20, 2018 at 04:23:00PM +0200, Willy Tarreau wrote:
>
> > > > Thus for you it's better to stick to a single listener, and if you want
> > > > to
> > > > increase the fairness between the sockets, you can reduce
> >
Hi Aurélien,
On Thu, Apr 19, 2018 at 06:16:37PM +0200, Aurélien Nephtali wrote:
> I guess I was sent off-track by the will to make something very flexible
> (at least in my mind) despite your multiple good examples, sorry about
> that.
No problem. That's exactly what design discussions are made f
On Fri, Apr 20, 2018 at 04:23:00PM +0200, Willy Tarreau wrote:
> > > Thus for you it's better to stick to a single listener, and if you want to
> > > increase the fairness between the sockets, you can reduce tune.maxaccept
> > > in
> > > the global section like below :
> > >
> > > global
> > >
On Fri, Apr 20, 2018 at 05:08:29PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Apr 20, 2018 at 03:55:25PM +0200, Willy Tarreau wrote:
>
> > On Fri, Apr 20, 2018 at 03:50:52PM +0300, Slawa Olhovchenkov wrote:
> > > Also some strange: after resart I see 100% busy on CPU#1 (other CPU as
> > > before -
On Fri, Apr 20, 2018 at 03:55:25PM +0200, Willy Tarreau wrote:
> On Fri, Apr 20, 2018 at 03:50:52PM +0300, Slawa Olhovchenkov wrote:
> > Also some strange: after resart I see 100% busy on CPU#1 (other CPU as
> > before -- from 0.05 to 0.4). This is busy loop over kevent:
> >
> > kqfd 11 cl 0 nc 0
On Fri, Apr 20, 2018 at 03:50:52PM +0300, Slawa Olhovchenkov wrote:
> Also some strange: after resart I see 100% busy on CPU#1 (other CPU as
> before -- from 0.05 to 0.4). This is busy loop over kevent:
>
> kqfd 11 cl 0 nc 0 eventlist 81340 nevent 200 timeout 0.200
> ret 11 errno 0
>
> ev
On Fri, Apr 20, 2018 at 03:50:29PM +0200, Willy Tarreau wrote:
> On Fri, Apr 20, 2018 at 02:39:28PM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Apr 20, 2018 at 09:46:23AM +0200, Willy Tarreau wrote:
> > > What you can do is to keep multiple listeners, each bound to a different
> > > thread, exact
On Fri, Apr 20, 2018 at 02:39:28PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Apr 20, 2018 at 09:46:23AM +0200, Willy Tarreau wrote:
> > What you can do is to keep multiple listeners, each bound to a different
> > thread, exactly like you did with processes :
> >
> >bind :80 ... process 1/1
>
On Fri, Apr 20, 2018 at 09:46:23AM +0200, Willy Tarreau wrote:
> > Hmm, may be I am nor clean.
> > In process mode all 8 CPU have load 0.18. In thread mode summary
> > average load still about 0.18, but distinct CPU load now different:
> >
> > 0: 0.13
> > 1: 0.15
> > 2: 0.07
> > 3: 0.40
> > 4: 0.
Am 19.04.2018 um 17:34 schrieb Willy Tarreau:
> Hi,
>
> HAProxy 1.8.8 was released on 2018/04/19. It added 8 new commits
> after version 1.8.7.
As usual the images are updated
https://hub.docker.com/r/me2digital/haproxy18/
https://hub.docker.com/r/me2digital/openshift-ocp-router-hap18/
If you a
On Fri, Apr 20, 2018 at 09:46:23AM +0200, Willy Tarreau wrote:
> On Fri, Apr 20, 2018 at 09:41:08AM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Apr 20, 2018 at 08:22:04AM +0200, Willy Tarreau wrote:
> >
> > > On Fri, Apr 20, 2018 at 09:11:47AM +0300, Slawa Olhovchenkov wrote:
> > > > > Try 1.8.8
On Fri, Apr 20, 2018 at 09:41:08AM +0300, Slawa Olhovchenkov wrote:
> On Fri, Apr 20, 2018 at 08:22:04AM +0200, Willy Tarreau wrote:
>
> > On Fri, Apr 20, 2018 at 09:11:47AM +0300, Slawa Olhovchenkov wrote:
> > > > Try 1.8.8, it contains the kqueue fix.
> > >
> > > Work (kqueue), nice!
> >
> > E
17 matches
Mail list logo
