-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0.0-M4
-
Fix Version/s: 2.0.8
-
Component/s: None
-
Labels:None
In the current code base, when accepting new connections, we pick a processor and register the news connection within the internal selector. In other words, we have as many selectors as we have IoProcessors.
This is a potential problem if some request cost a lot to be executed, as every requests waiting on this IoProcessor will be blocked.
It would be way better to use a single selector which dispatches requests to an Executor, as we will always have available threads ready to process the requests (unless the pool is saturated, but then we have a bigger issue ...)