JDK-8216366 : Add rationale to PER_CPU_SHARES define
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2019-01-08
  • Updated: 2022-11-30
  • Resolved: 2019-01-08
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.
JDK 11 JDK 13 Other
11.0.16-oracleResolved 13 b03Fixed openjdk8u372Fixed
Related Reports
Relates :  
JDK-8146115 - Improve docker container detection and resource configuration usage
Relates :  
JDK-8281181 - Do not use CPU Shares to compute active processor count
Description
The reason why PER_CPU_SHARES has been abstracted in the JVM to 1024 seems somewhat arbitrary. It resulted in this thread being raised:

http://mail.openjdk.java.net/pipermail/hotspot-dev/2019-January/036087.html

A bit of rationale should be added to the code to explain this situation.
Comments
A pull request was submitted for review. URL: https://git.openjdk.org/jdk8u-dev/pull/127 Date: 2022-10-03 09:57:22 +0000
18-10-2022
Retroactively adding jdk11u-fix-{request,yes} labels as this has been backported with JDK-8230305.
23-03-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk11u-dev/pull/840 Date: 2022-02-24 21:18:12 +0000
04-03-2022
URL: http://hg.openjdk.java.net/jdk/jdk/rev/3cdf4d5148a8 User: sgehwolf Date: 2019-01-08 19:09:50 +0000
08-01-2019
review thread: http://mail.openjdk.java.net/pipermail/hotspot-dev/2019-January/036137.html
08-01-2019