Details
-
Enhancement
-
Resolution: Duplicate
-
P3
-
7
-
generic
-
generic
Description
The startup team concerns itself with two types of Java startup scenarios:
* "Cold" start: Put simply, this is the scenario in which a user is running their first Java applet/application after a reboot. All portions of the JRE must be loaded from disk.
* "Warm" start: This is the scenario in which a user has already run a Java applet/application since booting up. Some/All of the JRE is already present in the OS's disk cache, and can be fetched from RAM instead of from disk.
Of course, warm start is much faster than cold start, by as much as an order of magnitude for minimal test cases.
An idea that has been tossed around for some time is to provide an option in the Java Control Panel that, when enabled, will "warm up" the JRE on boot-up/login. This technique is used by other applications, such as Mozilla, to improve application startup time. Ideally, this would eliminate the cold start case and "make every start a warm start".
In fact, developers have noticed that warm start is much faster, and have considered rolling their own mechanism to pre-warm the VM. For instance, see
http://forum.java.sun.com/thread.jspa?messageID=3962327
Of course, it would be easier to implement and provide much wider benefit if it were included in the JRE/JDK itself.
* "Cold" start: Put simply, this is the scenario in which a user is running their first Java applet/application after a reboot. All portions of the JRE must be loaded from disk.
* "Warm" start: This is the scenario in which a user has already run a Java applet/application since booting up. Some/All of the JRE is already present in the OS's disk cache, and can be fetched from RAM instead of from disk.
Of course, warm start is much faster than cold start, by as much as an order of magnitude for minimal test cases.
An idea that has been tossed around for some time is to provide an option in the Java Control Panel that, when enabled, will "warm up" the JRE on boot-up/login. This technique is used by other applications, such as Mozilla, to improve application startup time. Ideally, this would eliminate the cold start case and "make every start a warm start".
In fact, developers have noticed that warm start is much faster, and have considered rolling their own mechanism to pre-warm the VM. For instance, see
http://forum.java.sun.com/thread.jspa?messageID=3962327
Of course, it would be easier to implement and provide much wider benefit if it were included in the JRE/JDK itself.