[GLASSFISH-3660] <BT6595609>In-memory replication is not scaling beyond 4 instances Created: 20/Sep/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: failover
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: gfbugbridge Assignee: lwhite
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Solaris
Platform: Sun


Issuezilla Id: 3,660
Status Whiteboard:

91ur1Approved


 Description   

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6595609
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6595609
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description In-memory replication is not scaling beyond 4 instances. We are achieving good scalability from 2 to 4 instances. After that we are not seeing the similar scalability to 6 instances.
2 instances : 796.64 Hits/Sec
4 instances : 1461.09 Hits/Sec
6 instances : 1739.91 Hits/Sec

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description In order to determine where the scalability issues exist it is necessary to report what the scalability numbers are for these number of instances with the same load balancer, etc. with no memory replication. Until these numbers are provided it is premature to make conclusions about memory replication scalability or to know where to look for root cause.
Please update the bug.

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to [3-Medium]In-memory replication is not XXXXXX 2007-08-21 23:05:05 GMT

Priority changed from [3-Medium] to [4-Low]
This is not part of exit criteria hence not a release stopper so lowering priority to p4. We will nevertheless look into the scaling XXXXXX 2007-08-21 23:18:12 GMT

**********READ-ONLY Data from Bugtraq Ends********



 Comments   
Comment by gfbugbridge [ 20/Sep/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6595609
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6595609
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description In-memory replication is not scaling beyond 4 instances. We are achieving good scalability from 2 to 4 instances. After that we are not seeing the similar scalability to 6 instances.
2 instances : 796.64 Hits/Sec
4 instances : 1461.09 Hits/Sec
6 instances : 1739.91 Hits/Sec

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description In order to determine where the scalability issues exist it is necessary to report what the scalability numbers are for these number of instances with the same load balancer, etc. with no memory replication. Until these numbers are provided it is premature to make conclusions about memory replication scalability or to know where to look for root cause.
Please update the bug.

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to [3-Medium]In-memory replication is not XXXXXX 2007-08-21 23:05:05 GMT

Priority changed from [3-Medium] to [4-Low]
This is not part of exit criteria hence not a release stopper so lowering priority to p4. We will nevertheless look into the scaling XXXXXX 2007-08-21 23:18:12 GMT

**********READ-ONLY Data from Bugtraq Ends********

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Tue Jul 07 18:00:30 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.