Fedora 4 Clustering Testing Summary
Virginia Tech finished the Assessment Plan - Clustering and report our works in this page. The detail step-to-step procedures was documented in Fedora Cluster Installation in AWS.
Testing object 1: Verify the load balanced cluster setup using the updated Modeshape and Infinispan configuration.
Outcome: The Fedora 4 cluster can setup successfully in Amazon AWS using the updated Modeshape and Infinispan configuration (Deploying in AWS). Detail procedure please see 2014-10-14 Acceptance Test - High Availability cluster.
Testing object 2: Demonstrate the nodes joining and node leaving in the cluster.
Outcome: Once a node is configured to replication mode, it is easily to add that node into the cluster. Through the AWS EC2 load balancer, it is easily to add/remove node from the cluster. The load balancer can distribute the traffic evenly. The detail procedure please see 2014-10-14 Acceptance Test - High Availability cluster.
Testing object 3: Measure the single and cluster's throughput and response time.
Outcome: We use JMeter to simulate 100 users requesting Fedora server at the same time for a period. When the request are under the server load, the read requests response time are the same in both single and cluster.
Test Setup | Num. Requests | Test Duration (Seconds) | Average Response Time (ms) |
|---|---|---|---|
| Individual | 1000 | 60 | 38 |
| Cluster (3) | 1000 | 60 | 38 |
| Cluster (4) | 1000 | 60 | 38 |
| Individual | 3000 | 60 | 21 |
| Cluster (3) | 3000 | 60 | 27 |
| Cluster (4) | 3000 | 60 | 26 |
| Individual | 6000 | 60 | 21 |
| Cluster (3) | 6000 | 60 | 24 |
| Cluster (4) | 6000 | 60 | 23 |
| Individual | 10000 | 60 | 21 |
| Cluster (3) | 10000 | 60 | 23 |
| Cluster (4) | 10000 | 60 | 21 |
Detail report: Response Time Comparison of Single Fedora VS Clusters
Testing object 4: Continue increasing the load until server is unable to handle further requests from the client.
Outcome:
