Hazelcast vs Redis
- Hazelcast consistently outperforms Redis at scale. Hazelcast is faster than Redis at scale and the gap widens as the workload increases. The benchmarks show that as the workload increases (thus requiring more concurrent threads), Hazelcast maintains its high-throughput and low-latency performance.
- Published benchmarks that favor Redis do not use equal comparisons. In our latest benchmark reports, we call out several discrepancies in other benchmarks (not run by Hazelcast) that skew results in favor of Redis. Once the tests and configurations are normalized, Hazelcast performance outshines Redis. Also, Redis stops replicating data at high loads, which puts your system at risk for data loss (more details are available in this blog about tradeoffs in distributed systems).
- The Hazelcast architecture is the key to performance. Hazelcast was built for performance; for example, its multi-threaded architecture (Redis is single-threaded), near-cache, pipelining, and other capabilities give customers the highest throughput and lowest latency.
Recent Benchmark Results
Our latest performance benchmark tests compare Hazelcast Enterprise 3.12 versus Redis Open Source 5.0.3. The results are similar to past benchmarks, highlighting Hazelcast’s performance advantage at scale. The table below shows some key performance metrics:
|Key Metrics||Hazelcast Enterprise 3.12||Redis Open Source 5.0.3|
Throughput using 128 threads1
|1,190,000 ops/sec||660,000 ops/sec|
Throughput using 64 threads2
|636,000 ops/sec||614,000 ops/sec|
Throughput as load scaled3
(see chart below)
|Scaled linearly to 128 threads||Maxed out at 32 threads, performance degraded beyond that|