changeset 56153:42a13b4e9553

8230425: Shenandoah forces +UseNUMAInterleaving even after explicitly disabled Reviewed-by: rkennke
author shade
date Mon, 02 Sep 2019 12:10:21 +0200
parents 47ce198d5cf1
children be5865bda5b9
files src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp
diffstat 1 files changed, 1 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp	Mon Sep 02 11:31:12 2019 +0200
+++ b/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp	Mon Sep 02 12:10:21 2019 +0200
@@ -60,11 +60,9 @@
   }
 
   // Enable NUMA by default. While Shenandoah is not NUMA-aware, enabling NUMA makes
-  // storage allocation code NUMA-aware, and NUMA interleaving makes the storage
-  // allocated in consistent manner (interleaving) to minimize run-to-run variance.
+  // storage allocation code NUMA-aware.
   if (FLAG_IS_DEFAULT(UseNUMA)) {
     FLAG_SET_DEFAULT(UseNUMA, true);
-    FLAG_SET_DEFAULT(UseNUMAInterleaving, true);
   }
 
   // Set up default number of concurrent threads. We want to have cycles complete fast