Well, I thought wrong -- I see that peered sticky tables absolutely don't work with multiple processes, and sticky rules give a warning.
Would that be a feature on the roadmap? I can see that it's probably pretty non-trivial -- but would be super useful, at least for us. On Fri, May 2, 2014 at 9:51 AM, Jeff Zellner <j...@olark.com> wrote: > Hey all, > > We'd like to start terminating SSL (so that we can balance on url > parameters, primarily) on one of our busiest load balancer clusters. > Unfortunately, running with nbproc=1 our peak traffic causes us to > just-barely max out a CPU core -- just enough to severely degrade > latency/performance. > > There are a good deal of warnings in the docs about setting nbproc > 1 > -- unfortunately it seems to be our best option to handle the > increased load of SSL termination (we have plenty of unused cores, and > not much hope of getting better CPUs). > > We're using a sticky table that's peered between all the servers in > the cluster. I *think* that will still work with multiple processes... > So, aside from some extensive testing -- is there anything we should > be worried about with going nbproc > 1 in this configuration? > > Thanks! > > JZ
