How to deal with complex and time-consuming business logic in Netty?

problem description:

one or more channel we know will register on EventLoop . This EventLoop not only listens to events on Channel , but also handles business logic (including outbound logic) after the event arrives, that is, Netty handler calls on the same Channel are serial, as shown in the figure below. It causes some simple events to go unanswered (it could also be events on other channel ). So Netty is not recommended to handle complex business logic, such as database operations, in handler . What about time-consuming logic like this in Netty ?

clipboard.png

my thoughts

I think there should be two ways to deal with it

  1. uses a custom thread pool to encapsulate the time-consuming logic that needs to be processed into task and throw it into executor pool , but we know that having too many threads is not a good thing and will affect throughput.
  2. throw these tasks into the idle EventLoop so that you can make full use of the thread resources of Netty , but how can such code be implemented? is there a mature framework?
Netty java
Apr.29,2022
further study should be to find the answer!

EventLoop is called EventLoop because EventLoop requires cyclic listening for IO events, and any time-consuming logic may cause IO events to be unresponsive, so the second option is not advisable, although the general rule for Netty applications is to reuse EventLoop as much as possible to reduce thread creation overhead, but the premise is that the network IO sensitivity is not affected.

therefore, a special business thread pool is needed to deal with complex and time-consuming business logic. As long as the number of threads in the business thread pool and event loop thread pool is set reasonably, it will not have much impact on throughput. There are usually two ways to implement a business thread pool:

  1. in ChannelHandler , use the custom Java thread pool.
  2. with the business thread pool provided by Netty , ChannelPipeline has some add () methods that receive a EventExecutorGroup . If an event is passed to a custom EventExecutorGroup , it will be handled by some EventExecutor contained in this EventExecutorGroup . Netty provides a default implementation called DefaultEventExecutorGroup .

clipboard.png

does the business logic you refer to refer to the logic in the corresponding channelRead method in LoggingHandler in your code above? In your way, the thread that ultimately executes the logic in the channelRead method will be the thread in the thread pool you passed in?

Previous: Is there a tool for writing interface documents?

Next: Vue address bar directly enter URL to skip the login interface block is not successful.

css mysql arrays josn react html typescript webpack npm sass R objective-c .net sql-server jquery python-3.x angularjs django angular excel regex iphone ajax linux xml pandas vba spring database wordpress string wpf xcode windows bash postgresql oracle multithreading eclipse list firebase algorithm macos forms image scala visual-studio azure bootstrap spring-boot react-native python-2.7 docker performance function winforms matlab powershell apache dataframe api sqlite numpy rest shell selenium flutter dart maven loops qt swing android-studio csv express file class tensorflow sorting codeigniter perl
© 2021 CodesHelper
Advertising Contact us About us
Menu