Hazelcast with Azul Zing Benchmarks

Benchmark

Hazelcast with Azul Zing Benchmarks

Table of Contents

Overall RadarGun configuration

  • Test Duration – 15s Warmup, 20m Stress Test
  • Entry Sizes – 15%: 1024KB, 35%: 2048KB, 50%: 4096KB
  • Get / Put Ratio – 67% / 33%
  • 2 node cluster

Key Findings

Zing reduces full GC pauses.

So we would expect this to reflect in average latencies and, because larger full GCs are avoided, much more so in the largest max latencies. And this is what we found.

The average was reduced by 40%. The 99.99th percentile max latency was only 8ms for Zing but 55ms for HotSpot.

We conclude that Hazelcast with Azul Zing JVM has lower latency and much lower variability for more predictable latencies. This in turn allows Hazelcast to fit into tighter response time SLAs.

These results are applicable to small heap sizes where Hazelcast is storing small amounts of data of 500MB to 1.5Gb per node and are relevant to Hazelcast and Hazelcast Enterprise.

Note that in Hazelcast Enterprise HD, we store data off heap and only run with a small heap. So a similar benefit to one in these tests with 1 to 2GB heaps would be realized.

See below for summaries of results for 1GB and 2GB heap cases and the extensive test results further down.

1GB Heap Results Summary

Average response time for Get of 0.8ms versus for Get of .5ms for Zing

Max response for 99th percentile for Get of 2ms compared to 2ms for Zing

Max response for 99.99th percentile for Get of 40ms compared to 8ms for Zing

2GB Heap Results Summary

Average response time for Get of 0.8ms versus for Get of .5ms for Zing

Max response for 99th percentile for Get of 2ms compared to 2ms for Zing

Max response for 99.99th percentile for Get of 55ms compared to 8ms for Zing

Hotspot

Hotspot – 2 Node Cluster, 1GB Heap, 49% Heap Fill

jHiccup Report

Hotspot - 2 Node Cluster, 1GB Heap, 49% Heap Fill - jHiccup Report

RadarGun Report

Hotspot - 2 Node Cluster, 1GB Heap, 49% Heap Fill - RadarGun Report

Get Percentile

Hotspot - 2 Node Cluster, 1GB Heap, 49% Heap Fill - Get Percentile

Put Percentile

Hotspot - 2 Node Cluster, 1GB Heap, 49% Heap Fill - Put Percentile

Hotspot – 2 Node Cluster, 2GB Heap, 49% Heap Fill

jHiccup Report

Hotspot - 2 Node Cluster, 2GB Heap, 49% Heap Fill - jHiccup Report

RadarGun Report

Hotspot - 2 Node Cluster, 2GB Heap, 49% Heap Fill - RadarGun Report

Get Percentile

Hotspot - 2 Node Cluster, 2GB Heap, 49% Heap Fill - Get Percentile

Put Percentile

Hotspot - 2 Node Cluster, 2GB Heap, 49% Heap Fill - Put Percentile

Zing

Zing – 2 Node Cluster, 1GB Heap, 49% Heap Fill

jHiccup Report

Zing - 2 Node Cluster, 1GB Heap, 49% Heap Fill - jHiccup Report

RadarGun Report

Zing - 2 Node Cluster, 1GB Heap, 49% Heap Fill - RadarGun Report

Get Percentile

Zing - 2 Node Cluster, 1GB Heap, 49% Heap Fill - Get Percentile

Put Percentile

Zing - 2 Node Cluster, 1GB Heap, 49% Heap Fill - Put Percentile

Zing – 2 Node Cluster, 2GB Heap, 49% Heap Fill

jHiccup Report

Zing - 2 Node Cluster, 2GB Heap, 49% Heap Fill - jHiccup Report

RadarGun Report

Zing - 2 Node Cluster, 2GB Heap, 49% Heap Fill - RadarGun Report

Get Percentile

Zing - 2 Node Cluster, 2GB Heap, 49% Heap Fill - Get Percentile

Put Percentile

Zing - 2 Node Cluster, 2GB Heap, 49% Heap Fill - Put Percentile

Get the Benchmark

Oops!

There's supposed to be a form right here, but its been hidden by your adblocker. Please disable your adblocker so you can get the benchmark you came for.

Hazelcast.com

Menu