JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-307  -  Server scalability: improve the thread pool handling for NIO operations
Posted Aug 14, 2014 - updated Aug 28, 2014
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Enhancement
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Server
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0
Issue description
Currently, the server uses 5 NIO selectors for the various types of channels it handles. Each of them has a separate associated thread pool to handle non-blocking I/O, but there is only one configuration property to specifiy the size of this thread pool.

We need to revisit this design, and in particular consider the following:
  • should we have separate selectors?
  • should we have a separate thread pool for each?
  • should we consider a self-tuning strategy for the thread pool(s), eventually make it a pluggable strategy?
  • how should this be tested / benchmarked?



#3
Comment posted by
 lolo4j
Aug 28, 07:02
implemented in trunk revision 3342