United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6678929 Slow client JVM initialization at applet launch time (2)
6678929 : Slow client JVM initialization at applet launch time (2)

Details
Type:
Bug
Submit Date:
2008-03-23
Status:
Resolved
Updated Date:
2010-09-08
Project Name:
JDK
Resolved Date:
2008-04-29
Component:
deploy
OS:
generic
Sub-Component:
plugin
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
6u10
Fixed Versions:
6u10

Related Reports
Duplicate:
JDK-6680298 - plugin2 knuddels.de chat applet doesn't start
Relates:
JDK-6689174 - Plugin2: Tray icon open/close console menu broken if java console is closed externally
Relates:
JDK-6697433 - b23- java console content isn't initially well formatted with OOPP
Relates:
JDK-4145756 - connecting between Java socket and Unix Domain socket.
Relates:
JDK-6687899 - UnixDomainSocket.c breaks some Solaris builds
Relates:
JDK-6714877 - plugin2 printing is not working - CNFE sun/plugin2/main/client/WPluginEmbeddedFrame
Relates:
JDK-6678865 - Long command lines or applet parameter lists break new plug-in on Windows
Relates:
JDK-6668037 - Slow client JVM initialization at applet launch time
Relates:
JDK-6687820 - AF_UNIX pipe file doesn't get deleted on browser exit
Relates:
JDK-6687876 - Bootstrapping of new plug-in broken with startup changes

Sub Tasks

Description
CR 6668037 started to fix the slow launch time, and boost it about 200ms.

We figured, this is not sufficient, 
and need to measure the 'coast-coast' startup time,
which is from client JVM launch until the call of applet.init().

We have a 'gut' feeling, that this period is >> 1s,
at least on Unix.

While impl. the 2nd iteration to boost the performance,
the measurement showed, that the JVM launch time itself differs each time
and lies around 200-400ms.

The total launch time incl. JVM until applet.init()
was around 1.4s on GNU/Linux x86_64 running 32bit binaries.

Comments
SUGGESTED FIX

To minimize the overal startup time of a first applet launch,
we have to break the linear initialization sequence
and parallelize it.

It turns out, that some of the AWT functionality can be
'warmed-up' in parallel, while the IPC layer is initialized.

Another benefit is the usage of UnixDomainSockets (AF_UNIX)
and the now platform transport unification on NamedPipe.
The former SocketTransport initialization with it's
socket setup, took about 100ms.
2008-04-09 
EVALUATION

To minimize the overal startup time of a first applet launch,
we have to break the linear initialization sequence
and parallelize it.

It turns out, that some of the AWT functionality can be 
'warmed-up' in parallel, while the IPC layer is initialized.
2008-03-23


Hardware and Software, Engineered to Work Together