GridGain/Apache Ignite 1.5.0 vs Hazelcast 3.6 Benchmark
This is a comparison between GridGain 7.4/Apache Ignite 1.5.0 and Hazelcast 3.6 prepared using GridGain’s own benchmarking tool, Yardstick. As with our Hazelcast 3.6-Snapshot GridGain-7.4 Benchmark – EC2 benchmark, Hazelcast is faster in almost all benchmarks with less latency.
|EC2 Instance Type||c4.2xlarge|
|Number of Nodes||4|
|Yardstick Setup||3 server member nodes 1 driver member node (4 node cluster total)|
|Number of Threads||64|
|Test Duration (minutes)||5|
|Benchmark Framework*||Build yardstick from master https://github.com/hazelcast/yardstick, then the 2 dependent repos https://github.com/hazelcast/yardstick-ignite https://github.com/hazelcast/yardstick-hazelcast|
Differences to GridGain/Ignite Yardstick
We are synced with GridGain and Ignite Yardstick repos as they stood at 2 March 2015, except for 3 changes which we have submitted as pull requests: https://github.com/gridgain/yardstick/pull/10
The specific commit hashes matching our forks of their repos are:
These allow a variable size payload to be used. GridGain/ignite are testing only with 1 byte which is lower than anyone would actually use for a value.
BenchMark Results, Logs, config