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 (which cause a spike in connections to our db, and a raft of > other problems if we do this during heavy traffic). I strongly suggest to update your code to a more recent release, there have been a lot of bug fixes since dev15. Grab dev18 or better yet, the latest snapshot. It doesn't make sense to start troubleshooting on those obsolete releases, especially in the development branch. Lukas
