On Thu, Apr 19, 2018 at 06:08:51PM +0200, Lukas Tribus wrote: > Hello, > > > On 19 April 2018 at 14:31, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: > >> This is very useful, thank you. I'm seeing overall that when you're on > >> 1.7.10+kqueue and 1.8.5+poll the overall %user is the same. However > >> it's the system which makes a huge difference there (to be expected > >> with poll under load). However things are highly different when you > >> run with kqueue, this seems to indicate that we may be missing some > >> events in the kqueue loop or that we need multiple calls for some of > >> them to be processed, causing some suboptimal behaviour. There is > >> some important locking in 1.8 to deal with the fd cache which has been > >> revisited differently in 1.9. And the differences are important enough > >> not to be realisticly backportable. So it may be possible that what you > >> observe is a limit of the current 1.8 code, though we'll take a closer > >> look in case we find something. However since we haven't yet heard of > >> anything similar affecting epoll, it possibly is an issue affecting > >> only the kqueue code, so there's hope that we can spot something there. > > > > I am try 1.8.7 anf got same issuse. > > Try 1.8.8, it contains the kqueue fix.
Work (kqueue), nice! Average load same as for multiprocess, but load of distinct CPU from 0.06 to 0.39. Is this normal or expected? nbthread 8 cpu-map auto:1/1-8 0-7
