Ohloh by Black Duck

 Follow @ Meta   Join Now

Ratings and Reviews

  Analyzed 7 days ago based on code collected 7 days ago.
Community Rating
3.33333
   

Average Rating:   3.3/5.0
Number of Ratings:   3
Number of Reviews:   2

My Review of Cluster4Spring

You have not rated or reviewed this project. Click below to rate/review.  
0
 
New Review

Most Helpful Reviews

piotrga says:
Avatar
 
Failed under load  
1
   
written almost 6 years ago

I recently spent couple of weeks on writing a distributed Market Data Service for my client. The requirement was to distribute the load on couple of machines as MDS was meant to be used by few houndred nodes grid.

We investigated couple of options and decided to go for cluster4spring. It gave us load distribution, failover and dynamic discovery.

After couple of days of testing it turned out that we needed to switch the dynamic discovery off as some client nodes were failing to find MDS. This left us with predefined list of RMI endpoints. Unfortunately few days after we realised that some of the nodes were loosing connections to all MDS instances in the middle of the job. I ruled out the network problems. MDS instances were not overloaded, so they were not dropping connections. BTW it struck me that a single node could only handle 50 requests per second. Internal processing of request was taking no more than 1ms ( return map.get(key) ). I tried different config options but nothing helped.

more here: http://piotrga.wordpress.com/2007/08/22/rmicluster-working-alternative-for-cluster4spring/

2 out of 3 users found the following review helpful.

Did this review help you?

dylanrt says:
Avatar
 
Cluster4Spring  
0
 
written over 2 years ago

very convenient and reliable

Did this review help you?

Most Recent Reviews

dylanrt says:
Avatar
 
Cluster4Spring  
0
 
written over 2 years ago

very convenient and reliable

Did this review help you?

piotrga says:
Avatar
 
Failed under load  
1
   
written almost 6 years ago

I recently spent couple of weeks on writing a distributed Market Data Service for my client. The requirement was to distribute the load on couple of machines as MDS was meant to be used by few houndred nodes grid.

We investigated couple of options and decided to go for cluster4spring. It gave us load distribution, failover and dynamic discovery.

After couple of days of testing it turned out that we needed to switch the dynamic discovery off as some client nodes were failing to find MDS. This left us with predefined list of RMI endpoints. Unfortunately few days after we realised that some of the nodes were loosing connections to all MDS instances in the middle of the job. I ruled out the network problems. MDS instances were not overloaded, so they were not dropping connections. BTW it struck me that a single node could only handle 50 requests per second. Internal processing of request was taking no more than 1ms ( return map.get(key) ). I tried different config options but nothing helped.

more here: http://piotrga.wordpress.com/2007/08/22/rmicluster-working-alternative-for-cluster4spring/

2 out of 3 users found the following review helpful.

Did this review help you?

 
 

Project Summary

Code Data

SCM Data

Community Data

 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.