From c25e2fd8ec4dfee2d0d2ab354d198ec43d53ca6c Mon Sep 17 00:00:00 2001 From: Aleksey Shipilev Date: Mon, 2 Sep 2019 12:10:21 +0200 Subject: [PATCH] 8230425: Shenandoah forces +UseNUMAInterleaving even after explicitly disabled Reviewed-by: rkennke --- src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp b/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp index 751dad97b3b..eec0047cbbe 100644 --- a/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp +++ b/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp @@ -60,11 +60,9 @@ void ShenandoahArguments::initialize() { } // 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