JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-28  -  Asynchronous communication between servers
Posted Aug 08, 2012 - updated Yesterday (10:08)
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
    Feature request
  • 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
    Low
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
Currently, the communication between servers connected in p2p is synchronous. One of the implications is that a server can only dispatch one job at a time to another server, which can be a severe limit in terms of throughput.

We propose to refactor the server to server communication tio make it asynchronus and remove that limitation. This may involve additional functionalities to ensure the resulting jobs throughput is close to optimal: - additional information may need to be exchanged between servers, for instance how many nodes are available in the remote server - we might have to implement new load-balancing algorithms or modify existing ones - etc...

#9
Comment posted by
 lolo4j
Yesterday, 10:07
Implemented in trunk revision 4582,