Download the Benchmark

First name *

Last name *

Job title *

Company *

Phone number *

Company size *

Use case for Hazelcast *

What's your use case for Hazelcast: Other *

Role *

Role: Other *

Do you currently use Hazelcast software? *

Number of nodes in deployment (current or planned) *

Total memory allocation for deployment (current or planned) *

If you decide to use Hazelcast software, how soon will you deploy into production?

Experience level with Hazelcast *

Industry *

Email *

Country *

Communication Preferences *

All Communications - Include me on all communications listed below.

Technical Resources - Let me know of new software releases, technical resources and webinars.

Direct Communications - Contact me regarding Hazelcast products and services.

Events & Training - Let me know about upcoming events and training near me.

Newsletter - Send me the Hazelcast quarterly newsletter.

Security Updates - Send me security notifications related to Hazelcast products.

Comments

By submitting this form, you are agreeing to the Hazelcast Privacy Policy, and you are agreeing to be contacted about this request.

Manage your Hazelcast communication preferences here.

Benchmark

Hazelcast with Azul Zing Benchmarks

Table of Contents

Key Findings
- 1GB Heap Results Summary
- 2GB Heap Results Summary
Hotspot
- Hotspot – 2 Node Cluster, 1GB Heap, 49% Heap Fill
- Hotspot – 2 Node Cluster, 2GB Heap, 49% Heap Fill
Zing
- Zing – 2 Node Cluster, 1GB Heap, 49% Heap Fill
- Zing – 2 Node Cluster, 2GB Heap, 49% Heap Fill

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.