JDK-8368321 : Rethink compilation delay strategy for lukewarm methods
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 26
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-09-22
  • Updated: 2025-10-27
  • Resolved: 2025-10-27
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 26
26 masterFixed
Related Reports
Relates :  
Relates :  
Description
Current compilation delay strategy for lukewarm methods is based on a fixed threshold coefficient. It probably should also be make dependent on the compiler load. However, I now think that the threshold coefficient should also dynamically decrease with the load. Such that when the startup/warmup end (and there is no load on compilers) we should be free to get back to compile lukewarm methods.

So, the coefficient should rather be something like: scale = (1 + DelayCoefficient * load_average).
We need to port the load average compilation code from the leyden premain repo.
Comments
Changeset: 1e49376e Branch: master Author: Igor Veresov <iveresov@openjdk.org> Date: 2025-10-27 15:09:59 +0000 URL: https://git.openjdk.org/jdk/commit/1e49376ece39e8f9b5c72b58688b1e195a0014be
27-10-2025

A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/27926 Date: 2025-10-22 01:22:44 +0000
22-10-2025