JDK-8055809 : Early compilation of selected methods
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2014-08-22
  • Updated: 2017-01-30
  • Resolved: 2017-01-30
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 9
9Resolved
Related Reports
Duplicate :  
Description
Consider the following scenario: A customer knows that a subset of the methods of an application are often used. With tiered compilation enabled, however, all methods (including methods that are a priori known to be executed often) go through three phases: Each method is first interpreted, then compiled to C1, and is  then finally compiled to C2.

Compiling a subset of an application's methods using C1 right away could be beneficial, as C1 gathers the profiles necessary for C2 and is faster than the interpreter. This approach can improve application performance without increasing startup time too much.

This approach requires the capability of setting per-method compilation thresholds. Preferably, these method name/threshold pairs are read from a file.

Frequently executed methods are identified on sample run(s) of the VM. The set of frequently executed methods should be retrieved from the VM on the(se) sample run(s).

Comments
This was fixed by per-method usage of CompileThresholdScaling with JDK-8059606.
30-01-2017