On Thu, Jul 3, 2014 at 10:57 AM, Jai Gupta <j...@vidyamantra.com> wrote: > > > > On Thu, Jul 3, 2014 at 12:49 PM, Baptiste <bed...@gmail.com> wrote: >> >> On Thu, Jul 3, 2014 at 9:03 AM, Jai Gupta <j...@vidyamantra.com> wrote: >> > We use SSL so we would want to use Multiple CPU Cores as well. >> > We also use Peers for HA but it seems that peers can't be used in >> > multi-process mode (nbproc > 1). >> > We were hoping to use one core for everything except SSL and all >> > remaining >> > cores for SSL. >> > >> > In this case, only solution to I can think of is to use two instances of >> > haproxy, one for SSL with multiple cores and second for load balancing >> > and >> > peers with single core. >> > >> > Is this approach correct? Is there any other alternate? >> > >> > Jai >> >> >> Hi Jai, >> >> First question is what is the good reason you need to synchronize >> content of stick-tables using peers? > > > Hi Baptiste, > > We use stick-tables because our application needs sticky sessions (long > lived websocket connections) and are using peers because we need HA in event > if one haproxy crashes and if needed, we can also distribute load via DNS if > multiple haproxy have stick-tables info. > > For simplicity, we would want to use only one instance of haproxy per node > and was hoping haproxy to use multiple cores, at least for ssl. Something > similar to > http://brokenhaze.com/blog/2014/03/25/how-stack-exchange-gets-the-most-out-of-haproxy/ > but becasue we are using peers, haproxy won't allow multi-process mode. I am > hoping for a way by which we can limit peers to one core and use multiple > cores for other stuff. > >> >> Baptiste > >
Hi Jay, Could you share with us your stick configuration lines? I mean the stick table + the stick on, stick match, etc... Baptiste
