Why Netty use boss and work eventloop rather than one eventloop -
i've question netty. seems use boss eventloop keep accepting connection, , worker eventloop keep doing data i/o.
the source code showed 1 eventloop repeat calling select/poll/epoll. there more 1 eventloop burning cpu. why can't netty use 1 eventloop handle both server listen socket , accepted socket?
there architecture called seda. benefit of boss eventloop : thread used accept connection not blocked io threads used read data socket , work in handler. use executionhandler eventloop. netty changing , improving thread modeling. , changed lot in netty 4.
Comments
Post a Comment