-
Enhancement
-
Resolution: Won't Fix
-
P4
-
20
-
linux
A user has an environment with 50+ containerized java (JDK 17) running simultaneously on Linux. Some performance issue is observed and it is suspected that the root cause is the hardcoded timeout of 20 ms between re-readings of the OS cached metrics (memory limit and active processor count) that is expensive in a containerized environment. This timeout was introduced in JDK-8232207. In relation to this there is a request to have a possibility to set the refresh rate of the OS cached metrics at the launch time.
- csr for
-
JDK-8296126 Add +XX:OsCachedMetricsRefreshRate=<value> to set a refresh rate of the cached metrics
-
- Closed
-
- relates to
-
JDK-8232207 Linux os::available_memory re-reads cgroup configuration on every invocation
-
- Resolved
-
- links to
-
Review openjdk/jdk/10918