-
Enhancement
-
Resolution: Fixed
-
P3
-
1.2.0
-
None
-
1.2fcs
-
x86
-
windows_nt
-
Not verified
I am filing this as an RFE for tracking purposes. It has been
under investigation through SWAT for several weeks.
We obtained a considerable boost to core VM startup by disabling
the JIT while the VM is initialized. It turned out that the JIT was
JITing many classes which were only used during startup.
It appears we could achieve a similar, though smaller, startup boost
for small AWT programs by disabling the JIT during the startup code
in java.awt.Toolkit.getDefaultToolkit.
This pulls down AWT startup time from 5.3 to 4.9 seconds, a small
but useful improvement.
graham.hamilton@Eng 1998-08-07
- relates to
-
JDK-6744401 Consider removal of code disabling JIT in Toolkit.getDefaultToolkit
-
- Resolved
-