RE: CPU spike after restarting with -sf pid

2013-06-12 Thread Lukas Tribus
Is the latest snapshot really what you recommend for running in production? That depends ;) The thing is, if you already run the development branch (1.5), its likely that a snapshot contains more bugfixes - which you may be interested in (like [1]). Of course a snapshot on the other hand is

Re: CPU spike after restarting with -sf pid

2013-06-12 Thread Willy Tarreau
Hi Malcolm, On Tue, Jun 11, 2013 at 12:01:25AM +, Malcolm Handley wrote: That's sound advice. We'll upgrade soon and see whether anything changes. Is the latest snapshot really what you recommend for running in production? I was nervous about using a dev release but we desperately needed

RE: CPU spike after restarting with -sf pid

2013-06-10 Thread Malcolm Handley
That's sound advice. We'll upgrade soon and see whether anything changes. Is the latest snapshot really what you recommend for running in production? I was nervous about using a dev release but we desperately needed support for the proxy protocol. On Fri, Jun 07, 2013 at 03:16 PM, Lukas

Re: CPU spike after restarting with -sf pid

2013-06-10 Thread Cyril Bonté
Hi Malcolm, Le 11/06/2013 02:01, Malcolm Handley a écrit : I was nervous about using a dev release but we desperately needed support for the proxy protocol. If you only need the accept-proxy feature in the bind options and you are not comfortable with following the dev branch, I ported it to

RE: CPU spike after restarting with -sf pid

2013-06-07 Thread Lukas Tribus
Hi Malcolm, This works but we find that the new haproxy process uses a lot of cpu (100% of one core) for about 20 seconds after the restart. During this time it looks as if various queues fill up and haproxy logs fewer requests than normal. Once the cpu load drops we get a surge of requests