Hi Lukas, We tried the patch, it seems better. As soon as we switched nbproc off, throughput did not drop immediately like it did with earlier version, it started deteriorating slowly as traffic increased to peak hours, but eventually it did crash to the same levels as before.
CPU Usage was also better, only at peak hours I saw 100% CPU consumed by haproxy, other wise it would be between 60-80%. Please see attached image measuring througput, nbproc=20 until ~10PM, nbroc=1 from ~10PM to ~10AM, nbproc reverted to 20 from 10 AM onwards. Y-axis is speed in MBPS. Thanks Sachin On 4/21/16, 12:57 PM, "Lukas Tribus" <[email protected]> wrote: >Hi, > > >Am 21.04.2016 um 08:11 schrieb Sachin Shetty: >> Hi, >> >> any hints to further isolate this - we have deferred the problem by >>adding >> all the cores we had, but I have a feeling that our request rate is not >> that high (7K per minute a peak) and it will show up again as traffic >> increases. >> >> Thanks >> Sachin >> > >Try the fix 9c09ee87 [1], which is in snapshots since 1.6.4-20160412. > > >cheers, > >lukas > >[1] >http://www.haproxy.org/git?p=haproxy-1.6.git;a=commitdiff_plain;h=9c09ee87 >836bb2efd78a17f9b16d8afe0ec64018;hp=3bee40bfb7a35b624c5cc9d88daff5a9e3b99f >33 >[2] http://www.haproxy.org/download/1.6/src/snapshot/
