JDK-8243628 : Deprecate -XX:ForceNUMA option
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-04-27
- Updated: 2020-08-12
- Resolved: 2020-05-01
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 15 |
|---|
15 b22Fixed  |
Related Reports
|
CSR :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8244408 :
|
Description
The ForceNUMA VM option is a product option. It exists to force NUMA-related code paths to be taken on single-node machines, for use by developers. As such, it should be a development option rather than a product option. For (recent versions of) Linux this option is not needed at all, since nowadays NUMA systems can be faked e.g. by virtualization (qemu) or specifically on Linux by the NUMA emulation possibility (or a combination thereof). Other platforms may not be so featureful though. And for Windows, UseNUMA is forced off unless also -XX:+ForceNUMA, because the NUMA support on Windows is incomplete.
Comments
|