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