8230425: Shenandoah forces +UseNUMAInterleaving even after explicitly disabled
Reviewed-by: rkennke
This commit is contained in:
parent
5110530d5b
commit
c25e2fd8ec
@ -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
|
||||
|
Loading…
x
Reference in New Issue
Block a user