IV78388: JIT COMPILATION TIME EXCESSIVELY LONG FOR METHOD(S)

APAR status

• Closed as program error.

Error description

• Error Message: N/A
  .
  Stack Trace: N/A
  .
  

Local fix

• There are 3 ways in which this problem can be avoided, listed
  here from lowest to highest performance impact.
  If the specific methods are known, then inlining can be disabled
  on them. It is not recommended to disable inlining globally for
  performance reasons:
  -Xjit:{package/Class.method(signature)}(disableInlining)
  By setting this environment variable: TR_selfInliningLimit=1
  If environment variables cannot be used, then the following JVM
  option can be used: -Xjit:disableCHOpts,disableProfiledInlining
  

Problem summary

• The toString implementations of certain classes in the Java
  Class Library might cause excessive inlining and result in long
  compilation times. The issue is due to missing context (type
  information) in the heuristic used to determine which virtual
  method is likely the best choice to be inlined.  The heuristic
  picks the most common profiled target which would be an
  incorrect guess for given calls
  

Problem conclusion

• The JIT Compiler has been updated to fix the missing context and
  not spend excessive time during the inlining phase of method
  compilation.
  .
  This APAR will be fixed in the following Java Releases:
     8    SR2       (8.0.2.0)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  Service Refreshes and Fix Packs can be found at:
             https://www.ibm.com/developerworks/java/jdk/
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  JIT

• Fixed component ID

  620700124

Applicable component levels

• R130 PSY

     UP