Hey guys, On 15 January 2018 at 20:49, Willy Tarreau <[email protected]> wrote: > Samuel, > > While running a few tests with Christopher's patch in order to integrate > it, I managed to find a case where I'm still seeing quite a number of > calls to epoll_wait(0)=0. Studying the patch, I found that there's a > corner case which it doesn't address, which is where an fd is processed > and removed from the cache. By changing the test a little bit, I managed > to reduce the number of empty calls to epoll_loop by about 1/3 on my test > case. But I've also just noticed that at too low loads I can now miss some > events so I'm not sharing it now. And I don't know if the remaining ones > wakeups are valid so I want to study all this compared to a single-threaded > test. > > It's possible that sometimes we wake up too aggressively even maybe for > the tasts, though that's pure speculation. > > We'll keep you updated on this.
Also consider this report from discourse: https://discourse.haproxy.org/t/haproxy1-8-3-dynamic-dns-resolvers-problem/1997 Haproxy 1.8.3 with nbthread > 1 and while reloading, DNS resolutions fails. Its possibile this was working in 1.8.2, but I'm waiting for confirmation. Not sure if the issue here could be related to DNS resolutions (and it's FDs). cheers, lukas
