From 86e2a82e1c2bec4321637d66f9c43c1705aa5424 Mon Sep 17 00:00:00 2001 From: Yoshikazu Nojima Date: Sat, 15 Apr 2023 02:30:37 +0900 Subject: [PATCH] Correct a minor error in native-reference.adoc --- docs/src/main/asciidoc/native-reference.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/native-reference.adoc b/docs/src/main/asciidoc/native-reference.adoc index ebb42fa736d1f..ab2cadd835fba 100644 --- a/docs/src/main/asciidoc/native-reference.adoc +++ b/docs/src/main/asciidoc/native-reference.adoc @@ -58,7 +58,7 @@ This means that GraalVM’s adaptive GC policy tries to aggressively trigger GCs Up to version 2.13, Quarkus used the “space/time” GC collection policy by default, but starting with version 2.14, it switched to using the “adaptive” policy instead. The reason why Quarkus initially chose to use "space/time" is because at that time it had considerable performance improvements over "adaptive". -Recent performance experiments, however, indicate that the "space/time" policy can result in worse out-of-the-box experience compared to the "space/time" policy, +Recent performance experiments, however, indicate that the "space/time" policy can result in worse out-of-the-box experience compared to the "adaptive" policy, while at the same time the benefits it used to offer have diminished considerably after improvements made to the "adaptive" policy. As a result, the "adaptive" policy appears to be the best option for most, if not all, Quarkus applications. Full details on this switch can be read in link:https://github.com/quarkusio/quarkus/issues/28267[this issue].