Open Source Projects:

Performance Benchmarks

Hazelcast vs Gridgain

Pricing
Chat
Contact
Back to top
Overview

Overview

Hazelcast and GridGain provide performance and scalability for in-memory data grid use cases. Developers can embed instances in the application server or as process instances on dedicated hardware. Any member of a cluster can communicate with any other. Data is replicated across physical servers for redundancy. Both Hazelcast and Apache Ignite/GridGain support distributed and replicated Caches, Query and Execution.

But in almost all other in-memory computing and stream processing use cases, Hazelcast is the better choice. Hazelcast supports Reliable Topics, Ringbuffers, Maps, MultiMaps, Sets, Lists, HyperLogLogs, and EventJournal out of the box. Also, the Hazelcast CP subsystem is a component of a Hazelcast cluster that builds an in-memory strongly consistent layer. Its data structures always maintain linearizability and prefer consistency over availability during network partitions.

Hazelcast has run performance benchmarks against GridGain and makes the following assertions:

  • Hazelcast consistently outperforms Gridgain at scale. Benchmarks show that Hazelcast has up to 90% more throughput with lower latencies.
  • Published benchmarks by GridGain are flawed. GridGain benchmarks used different configurations between their technology and Hazelcast, unfairly skewing the results. In fair and equivalent tests, Hazelcast shows a significant performance advantage over GridGain.
  • Hazelcast is committed to delivering high performance. Hazelcast strives for fair benchmarks and welcomes independent benchmarking. Hazelcasts not only publishes benchmark results but also documents the environment and test tools so anyone can confirm the performance advantage themselves.
Results

Recent Benchmark Results

Our latest performance benchmark tests compare Hazelcast Enterprise 3.6 versus GridGain 7.4 (Apache Ignite 1.4.1). The table below shows some key performance metrics:

Key Metrics

Hazelcast

Gridgain (Apache Ignite)

JCache Put

Avg. operations/sec (higher is better)

  • Avg: 179,568.33
  • Min: 168,851
  • Max: 190,782
  • SD: 5041.38

Latency in ns (lower is better)

  • Avg: 1,425,996.59
  • Min: 1,340,742.45
  • Max: 1,514,856.81
  • SD: 40,249.02

Avg. operations/sec (higher is better)

  • Avg: 155,757.25
  • Min: 147,060
  • Max: 161,154
  • SD: 2959.46

Latency in ns (lower is better)

  • Avg: 1,644,003.01
  • Min: 1,586,960.89
  • Max: 1,756,147.92
  • SD: 32,433.89

JCache Put/Get

Avg. operations/sec (higher is better)

  • Avg: 111,997.38
  • Min: 98,377
  • Max: 119,243
  • SD: 4930.86

Latency in ns (lower is better)

  • Avg: 2,288,613.67
  • Min: 2,146,167.95
  • Max: 2,601,313.86
  • SD: 104,725.79

Avg. operations/sec (higher is better)

  • Avg: 99,411.22
  • Min: 95,286
  • Max: 102,625
  • SD: 1627.75

Latency in ns (lower is better)

  • Avg: 2,575,413.98
  • Min: 2,494,973.05
  • Max: 2,704,224.53
  • SD: 42,252.43
Additional Resources

Free Hazelcast Online Training Center

Whether you're interested in learning the basics of in-memory systems, or you're looking for advanced, real-world production examples and best practices, we've got you covered.