I found glassfish startup performance issue in Windows platform.
This is introduced byJDK-8248657, which affects AARCH64 Windows.
In this fix, always WaitForSingleObject() is called, but it is
low performance in multi processes with heavy stress.
OS: Windows Server 2016
Memory: 8GB
CPU: Intel Xeon Platium 8260 2.4GHz (4CPU)
8 instances in cluster:
glassfish 7 with JDK21: start-cluster takes 95-105 sec
glassfish 7 with JDK21 revertJDK-8248657: start-cluster takes 85-95 sec
So, I propose threadCritical_windows.cpp move to os_cpu, and revert
JDK-8248657 at threadCritical_windows_x86.cpp.
This is introduced by
In this fix, always WaitForSingleObject() is called, but it is
low performance in multi processes with heavy stress.
OS: Windows Server 2016
Memory: 8GB
CPU: Intel Xeon Platium 8260 2.4GHz (4CPU)
8 instances in cluster:
glassfish 7 with JDK21: start-cluster takes 95-105 sec
glassfish 7 with JDK21 revert
So, I propose threadCritical_windows.cpp move to os_cpu, and revert
- relates to
-
JDK-8248657 Windows: strengthening in ThreadCritical regarding memory model
-
- Resolved
-
- links to
-
Review openjdk/jdk/17682