Hi Willy, I tested against the latest version in the haproxy source repo. Things got significantly worse. Even median latencies have shot up to 150ms ( compared to 4ms for haproxy 1.8) p99 shot up above 1second. One strange thing I observed in the stats page is nbthread shows up as 64 ( its 1 for HAProxy 1.8). I am using the exact same configuration across both versions. ctime , rtime are reporting higher values for 2.0 ( though 1.8 is fine against the same backends at the same time)
-Ashwin Thanks, Ashwin On Fri, Mar 22, 2019 at 11:03 AM Ashwin Neerabail <ash...@box.com> wrote: > Hey Willy, > > Thats great news. Thanks for the quick action. > I will verify and get back. > > Thanks, > Ashwin > > On Fri, Mar 22, 2019 at 10:19 AM Willy Tarreau <w...@1wt.eu> wrote: > >> Hi Ashwin, >> >> We have found the root cause of this. The H2 streams were not getting >> the fairness they deserved due to their wake-up ordering : it happened >> very often that a stream interrupted on a ux buffer full condition could >> be placed at the end of the list and/or its place preempted by another >> stream trying to send for the first time. >> >> We've pushed all the fixes for this in 2.0-dev for now and I'll backport >> them to 1.9 early next week. It would be nice if you could give it a try >> to confirm that it's now OK for you. >> >> Cheers, >> Willy >> >
