From 2493200f66fd9e1c108266f272805f20d3a53a04 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 18 Dec 2024 15:28:03 +0000 Subject: [PATCH] GH issues 1428: remove reference to ZGC being experimental [v/5.3] (#1434) Backport of https://github.com/hazelcast/hz-docs/pull/1433 https://github.com/hazelcast/hz-docs/issues/1428 Co-authored-by: Rob Swain --- docs/modules/ROOT/pages/capacity-planning.adoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/modules/ROOT/pages/capacity-planning.adoc b/docs/modules/ROOT/pages/capacity-planning.adoc index 681d26b62..7a9b42983 100644 --- a/docs/modules/ROOT/pages/capacity-planning.adoc +++ b/docs/modules/ROOT/pages/capacity-planning.adoc @@ -616,9 +616,7 @@ collector. We found it to work well without any tuning parameters. Its current downside is that it handles less throughput compared to G1 and, being non-generational, doesn't work well if you have a lot of static data on the heap (for example, if your data pipeline has a `hashJoin` -stage). ZGC is an experimental collector under intense development, so -you can expect further improvements, including generational GC behavior, -in the future. +stage). In our tests we found that as of JDK version 14.0.2, the other low-latency collector, Shenandoah, still did not perform as well as ZGC