You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2019/07/11 23:32:13 UTC

[GitHub] [incubator-pinot] siddharthteotia opened a new issue #4427: Consider using epoll based event loop in Netty when Pinot runs on Linux systems

siddharthteotia opened a new issue #4427: Consider using epoll based event loop in Netty when Pinot runs on Linux systems
URL: https://github.com/apache/incubator-pinot/issues/4427
 
 
   Netty provides the asynchronous event based multiplexing over connections in 3 different flavors -- java nio selector, epoll (Linux only) and kqueue (BSD only). 
   
   epoll and kqueue have been the new variants out there and are known to be much more scalable than select() especially because at high concurrency, selector has to do a linear search through the set of registered socket descriptors to see which descriptors had some activity. This tends to become a costly O(n) operation with the increase in number of connections
   
   In epoll(), there is no cost for detecting activity on sockets where there was no activity since it uses kernel level callbacks.
   
   Some info here -- https://stackoverflow.com/questions/17355593/why-is-epoll-faster-than-select

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org