JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
task_small.png
CLOSED  Task JPPF-572  -  Performance, endurance and stress testing
Posted Jan 17, 2019 - updated Mar 28, 2019
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Task
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Performance
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.1
Issue description
Given the major changes in the upcoming 6.1 release, in particular Feature request JPPF-548 - Drop support for JDK 7 and switch to JDK 8 or later, Feature request JPPF-549 - Asynchonous communication between server and client and Feature request JPPF-564 - Asynchronous communication betwen node and driver, it is important to check for possible regressions of the performance and health indicators.

Some specific points to check:
  • load-balancing performance, how is load-balancing impacted by the fact that nodes can now process multiple jobs concurrently?
  • look for memory leaks; I'm hoping endurance tests will help with that
  • on the client side, attempt to measure the performance impact of single vs. multiple connections with multiple concurrejt jobs

#2
Comment posted by
 lolo4j
Mar 09, 05:21
Related commit: fixed node connection context leak in the driver
#3
Comment posted by
 lolo4j
Mar 17, 06:52
Numerous fixes during resilience testing in commit 0a81647