IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools

JIT and AOT problem determination

You can use command-line options to help diagnose JIT and AOT compiler problems and to tune performance.

• Diagnosing a JIT or AOT problem
  Occasionally, valid bytecodes might compile into invalid native code, causing the Java™ program to fail. By determining whether the JIT or AOT compiler is faulty and, if so, where it is faulty, you can provide valuable help to the Java service team.
• Performance of short-running applications
  The IBM JIT compiler is tuned for long-running applications typically used on a server. You can use the -Xquickstart command-line option to improve the performance of short-running applications, especially for applications in which processing is not concentrated into a few methods.
• JVM behavior during idle periods
  You can reduce the CPU cycles consumed by an idle JVM by using the -XsamplingExpirationTime option to turn off the JIT sampling thread.

Parent: Using diagnostic tools

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.