GridGain 2.1.1 (comparison of the grid/cloud computing frameworks - part II)
Test environment
During fail-over tests we used the same test environment as in the part I of our comparison. However, we simulated node failures during our tests in the following order:
- intel4 went down after 60 seconds from the beginning of computations
- intel3 went down after 180 seconds from the beginning of computations
- intel2 went down after 300 seconds from the beginning of computations
Code
During fail-over tests we used the same code as in the part I of our comparison. The only thing that has changed was new fail-over hook just before task generation phase. It allowed us to precisely synchronize the test environment.
You can find all the code in our repository: http://dacframe.org/lab
Results
You can see all the results with std deviation and average values on the following table:
GridGain 2.1.1 ExecutorService <-->| Average | 568 426.60 |
| Std Deviation | 33 317.41 |
| Computation time | |
|---|---|
| 568 851.00 | |
| 545 554.00 | |
| 561 759.00 | |
| 563 800.00 | |
| 548 991.00 | |
| 561 471.00 | |
| 559 533.00 | |
| 559 343.00 | |
| 553 803.00 | |
| 661 161.00 |
As you can see on the above table, only std deviation is much bigger in the fail-over test than in our first comparison. Average time increased from 338 310.40 by 68.02%, std deviation increased from 8 051.70 by 313%. This means, that GridGain is quite immune to unexpected node failures.
CPU
CPU usage (%user) gathered on all machines:
CPU usage (%system) gathered on all machines:
Memory
Memory usage gathered on all machines:
Network
Network usage (received bytes/s) gathered on all machines:
Network usage (transmitted bytes/s) gathered on all machines:
