Home > javafx > JavaFX – Applet Startup Time

JavaFX – Applet Startup Time

Bookmark and Share

We keep getting various numbers related to JavaFX applet startup time. Yes this is very important and we need a consistent way to measure this and compare. Here is an attempt..


When the page is loaded, the system time is noted using JavaScript. Time is again noted once Applet is loaded. Difference between time obtained in Applet and JavaScript is computed to be startup time. I think this will be fair and consistent way to measure startup time. This requires JavaSE 6 Update 10 and above. It will be good to try out a few times and get the average number..

User Without JavaFX
Rakesh Menon 45 3.00 0.70
Pär Dahlberg 7.27 0.66
Julien Buret 1.71 0.32
cozmint 7.83 1.55
Philippe Lhoste 3.42 0.98
Ernie Kent 4.73 0.66
Carl Dea – FF 5.74 0.63
Carl Dea – IE 3.34 0.74
Simon Brocklehurst 3.12 0.79
Tom Eugelink 2.68 0.64
Guido 2.56 0.62
GC – WinXP-64bit FF-64bit Error
Carl Antaki 4.06 0.67
Nick Apperley 3.27 0.83
Andy Xie 47 8.32 1.05
Wojciech Halicki-Piszko 4.45 0.8
Endre Stølsvik 72 3.80
Chui Tey – Chrome 6.95 2.86
Chui Tey – MSIE 8.0.6001.18702IS 3.22 0.70
Chui Tey – FF 3.0.10 4.13 0.70
JosK (Intel Core 2CPU 4300@1.8GHZ (1,93GB)
512RAM) – Chrome
4.26 4.08
JosK (Intel Core 2CPU 4300@1.8GHZ (1,93GB)
512RAM) – Chrome
3.98 1.05
JosK (Intel Core 2CPU 4300@1.8GHZ (1,93GB)
512RAM) – IE 8.0.6001.18702
8.33 1.06
Jonathan (Quad Core Q9300 @ 2.5GHZ, 4GB ram JRE 1.6u15) 15.50 0.52
Thierry (2 year olds windows dual core basic PC) 17.50 3.10
Robrecht (Windows xp SP2 Intel Core 2 cpu T5600 @ 1,83GHz, 2GB Ram jre: 1.6.0_15) 4.83 2.80 0.62
Venkateswara Rao Desu (Fedora 9 JDK 1.6_10) Applet not initialized
André Costa 1.91 0.42
Joeri Sykora (jdk 1.6.0_16 in Firefox 3.5.3) 1.02 0.65
Thustle (1.6.0_16 on Chrome v3 on Vista 32bit Intel Core2 Quad Q6600 2.4GHz 4GB) 9.30 0.74
Vance (Intel Core 2 Duo P8700 2.53GHz/1066Mhz RAM:4GB, DDR3, 1067 MHz, Ubuntu 9.10, FireFox 3.5.5, JRE: 1.6.0_15, Connection: comcast high-speed cable) 7.6 2.3 0.3
Venkateswara Rao Desu (Fedora 11 Firefox 3.5.5 Sun Java Plugin) 17.00 0.70
Venkateswara Rao Desu (Windows XP Java 1.6.0_18) 9.3 0.38
Jor (WinXP, FF 3.5.7, Java 1.6.0_17) 36 0.21
Galien (IE8 64 bit, 1.6_18 Vista 64bit, intel i720, sata 10k rpm) 11.92 0.28 1.17
Galien (FireFox 3.6 32 bit, 1.6_18 Vista 64bit, intel i720, sata 10k rpm) 12.10 0.15 0.15


  • Without JavaFX Runtime – After clearing Java Web Start cache – [ javaws -uninstall ] May have to wait for sometime as clearing process may be running in background. This is the time taken to download JavaFX runtime and load the applet.
  • Load Applet – Launch browser and load applet (JavaFX runtime already installed)
  • Re-Load Applet – Re-load the page after loading applet
  • Duration – specified in seconds

Please launch the applet and let me know the start-up time with system configuration and connection speed.. Thanks in advance..

Categories: javafx Tags: ,
  1. August 31, 2009 at 4:23 AM

    I got 7.265s on a Core2 Duo 2Ghz with 3Gb RAM running Eclipse, Firefox etc with a bit over 1Gb physical memory free.

  2. Julien Buret
    August 31, 2009 at 6:00 AM

    first time : 1.71s , re-load : 0.32s – Core2 Duo , 4Gb RAM, ubuntu 9.04, firefox, java 6u14, 10Mb/s

  3. cozmint
    August 31, 2009 at 1:40 PM

    load: 7.83
    reload: 1.545
    Athlon64 3200+, 3 GB, running 12 Firefox windows

  4. August 31, 2009 at 11:36 PM

    Right, forgot the reload 🙂
    Cleared the cache and got: 4.16s
    Reload: 0.66s

  5. August 31, 2009 at 11:56 PM

    @Pär Dahlberg "Cleared the cache and got: 4.16s" that value looks a bit too low. Also fresh load takes more time than that (7.17). May be because the javaws cache was not cleared completely?

  6. September 2, 2009 at 10:59 AM

    Got 3.42 on first load, 0.98 on second one. Did the javaws -uninstall stuff and I regret it, as I forgot JavaFX 1.2.1 is in the process of being deployed (see http://forums.sun.com/thread.jspa?threadID=5403636 thread), and the files are not currently available, so I have no more JavaFX runtime… 😦 (logo is spinning infinitely).

  7. September 2, 2009 at 10:06 PM

    @Philippe Lhoste Really sorry about "javaws -uninstall", I didn’t anticipate this issue. I tried now its still installing 1.2 runtime.

  8. September 3, 2009 at 5:52 PM

    3.4GHz Intel, Windows XP, DSL @ 1360 kbps
    Load Applet = 4.73
    Relaod = 0.653

  9. September 4, 2009 at 9:46 PM

    CPU: Dell Inspiron XPS Pentium 4 CPU 3.40GHz 3.39 GHz, and 1 gig of ram
    OS: Windows XP SP3
    Java: 1.6.0_16
    JavaFX: 1.2
    Browser: Firefox 3.5.2
    First time: 5.742 s
    Re-load time: 0.73 s
    Re-load time: 0.53 s
    Browser: IE 7.0.5730.13
    First time: 3.344 s
    Re-load time: 0.735 s
    Re-load time: 0.75 s

  10. September 4, 2009 at 10:14 PM

    Load applet – 3.12 seconds
    Reload applet – 0.79 seconds
    Windows Vista, Firefox 3.5.2, Java 6 Update 15
    Intel Core 2 Duo 2GHz, 2GB RAM.

  11. September 6, 2009 at 10:00 PM

    Thanks to all. Looking forward to have more entries, this will help to baseline and compare with next JavaFX release.

  12. Tom Eugelink
    September 6, 2009 at 11:17 PM

    Intal Q6600 @ 2.40GHz, Vista 64
    startup: 2.678
    reload: 0.641

  13. September 7, 2009 at 2:46 AM

    Hi Rakesh,
    It took on my machine at work
    2.596 sec.
    PC Configuration:
    Quad Core, 2.66 Ghz, 3.49 GB Ram, Windows XP, JVM1.6.0_B014, FF3.0.13.
    Network configuration is:
    Download avg 33.4 Mb/s

  14. September 7, 2009 at 2:48 AM

    Forgot relaunch time: 0.612 s

  15. Gc
    September 7, 2009 at 3:18 AM

    Never started. I see the Java logo with the rotating blue circle.
    Windows XP 64 bits, using Firefox 64bits (shiretoko), Jdk1.6_016 64bits, and behind a proxy.
    No log in Java console.

  16. September 7, 2009 at 6:16 AM

    Safari 4 on Mac OS 10.6
    4GB RAM Core Two Duo
    Java 6 Update 15
    4.06s cold start
    0.67s reload
    There seems to be a problem with the refresh of the progress bar to the text as it stays forever until I resize the browser.

  17. Nick Apperley
    September 7, 2009 at 6:14 PM

    – Athlon64 (1GHz) with 1GB of RAM
    – Ubuntu 8.04 (32 bit) with NetBeans 6.7.1 running in the background
    – Applet loaded in Firefox 3.0.13 using JRE 1.6 (Update 14)
    Applet Results
    Initial Applet Load – 3.27s
    Applet Reload – 0.83s

  18. Andy Xie
    September 7, 2009 at 9:32 PM

    Online Results
    Without Runtime – 46.956s
    Initial Applet Load – 8.312s
    Applet Reload – 1.049s
    Offline Result
    Without Runtime – 15.892s
    Initial Applet Load – 8.873s
    Applet Reload – 1.114s

  19. September 9, 2009 at 11:57 PM

    Pentium 4HT
    Windows XP Pro
    MS Outlook, Chrome, Adobe Bridge, Spark
    Java Console showing
    Initial Applet Load ~22 s
    Applet Reload ~0.8 s

  20. September 9, 2009 at 11:59 PM

    Same spec without Java Console starting first – 4.445 s

  21. September 10, 2009 at 1:23 AM

    @Wojciech Halicki-Piszko I think the initial applet load of ~22 s was due to 1.2.1 patch update

  22. Endre Stølsvik
    September 11, 2009 at 3:43 AM

    Apparently had to install the JavaFX junk:
    71.898 s
    Reload (hit reload-button of browser, right?): 3.797

  23. September 11, 2009 at 4:20 AM

    Windows XP, Intel Core Duo, 4Gb RAM
    Load Applet, Reload Applet, Browser
    6.95 2.86 Chrome
    3.22 0.70 MSIE 8.0.6001.18702IS
    4.13 0.70 FF 3.0.10

  24. JosK
    September 16, 2009 at 5:01 PM

    4.264/4.079 Chrome
    3.983/1.046 Chrome
    8.329/1.062 IE 8.0.6001.18702
    Intel Core 2CPU 4300@1.8GHZ (1,93GB)

  25. Jonathan
    September 23, 2009 at 10:48 AM

    Quad Core Q9300 @ 2.5GHZ, 4GB ram
    JRE 1.6u15
    Initial Applet Load – 15.5s
    Applet Reload – 0.519s

  26. Thierry
    September 23, 2009 at 4:45 PM

    I got :
    First visit –> 17,5 seconds
    Second : 3,1s
    I have a 2 year olds windows dual core basic PC.
    From my point of vue, 17,5 seconds is really too much for a Web embedded application.
    I have the same problm with my application :
    The first attemp is too long.
    I also commented my frustration in the Thread here.
    ->And I do repeat myself gain :
    for a standard rich-web-applet, I think java jre takes too long to load code.
    Perhaps it is because most applets have some API to load (some too heavy jars I suppose).
    I will try to use pack200 but at least without pack200 we can forget about any success on the WEB era.
    Don’t forget that the majority of the web PC :
    1) Are older than 2 years
    2) the broadband is not optic fiber
    Thus we get MOST of today’s Rich-Applet taking more than 15 seconds to load on an average machine. Too long comparing to Flash.
    I will try to Jar200 my jars, to see if for my application it does make a difference for the first loading. I am praying for it ……..

  27. Robrecht
    September 30, 2009 at 12:47 AM

    I don’t know why, but it fails on firefox 3.5.3 The loading icon is still running…
    In IE 7
    First time 4,83 seconds, reload 0,621 seconds, after browser restart 2,8 seconds.
    Windows xp SP2
    Intel Core 2 cpu T5600 @ 1,83GHz, 2GB Ram
    jre: 1.6.0_15

  28. Venkateswara Rao Desu
    September 30, 2009 at 7:26 AM

    Mine is Fedora 9
    Applet not initialized
    JDK 1.6_10

  29. André Costa
    September 30, 2009 at 1:58 PM

    First time: 1.909 s
    Re-load: 0.413 s

  30. Joeri Sykora
    October 7, 2009 at 7:26 AM

    I got the following timings using jdk 1.6.0_16 in Firefox 3.5.3:
    First time: 1.015 s
    Reload: 0.653 s
    Machine: Windows Vista, Intel Core2 Duo P8700 @ 2.53GHz with 4GB RAM.

  31. Thustle
    October 15, 2009 at 12:41 AM

    First Time: 9.298
    Reload: 0.734
    1.6.0_16 on Chrome v3 on Vista 32bit.
    Intel Core2 Quad Q6600 2.4GHz 4GB

  32. Vance
    November 14, 2009 at 7:27 PM

    Processor:Intel Core 2 Duo P8700(2.53GHz/1066Mhz
    RAM:4GB, DDR3, 1067 MHz
    OS:Ubuntu 9.10 With all updates
    Browser:FireFox 3.5.5
    Java version:
    java version "1.6.0_15"
    Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
    Java HotSpot(TM) Server VM (build 14.1-b02, mixed mode)
    First-start up time:
    After closing out browser:
    After refreshing and testing a few times in a row:
    around .3s
    I think Sun has some work to do. I know .3s is all that bad, but 7.6 is.

  33. Vance
    November 14, 2009 at 7:31 PM

    I forgot to include the connection speed. I am on comcast high-speed cable. Here are the results form Speedtest.net. I don’t know if that is good source, but maybe its useful:

  34. Venkateswara Rao Desu
    December 1, 2009 at 9:14 PM

    Fedora 11 Firefox 3.5.5 Sun Java Plugin
    Wothout JavaFx : 17.0 Sec
    Reload the same page and click start : 0.701 Sec

  35. February 15, 2010 at 9:58 AM


    I got this error when using Windows XP, FF, jre 1.6_18 after a clear cache. Before I show you the error I wanted mention that I was able to reproduce it. And I have a work around if this happens to users.

    Step 1: load applet (observing it running fine) 1st load.
    Step 2: Go to Java Control Panel -> General -> temp internet files -> Settings button -> Delete files button -> OK button.
    Step 3: reload same page, F5 (reload applet)
    Step 4: The console produces the error below:

    HTML_TIME : 1266207344537
    APPLET_TIME: 1266207346388
    LOAD_TIME : 1851.0 Milli-Seconds
    exception: JNLP file error: Startup_browser.jnlp. Please make sure the file exists and check if “codebase” and “href” in the JNLP file are correct..
    java.io.FileNotFoundException: JNLP file error: Startup_browser.jnlp. Please make sure the file exists and check if “codebase” and “href” in the JNLP file are correct.
    at sun.plugin2.applet.JNLP2Manager.loadJarFiles(Unknown Source)
    at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
    Exception: java.io.FileNotFoundException: JNLP file error: Startup_browser.jnlp. Please make sure the file exists and check if “codebase” and “href” in the JNLP file are correct.

    The work around is to close tab or Firefox and load page again.

    I hope this helps.


    • February 15, 2010 at 10:24 AM

      @Carl Its a bug. It may be because conflict between the browser cache and deployment cache. It tries to load the file again from cache. Ideally it must try to download the file again from source (if its missing from cache). Users will not face this issue unless they explicitly remove entry from the cache. So may not be a major issue. I’ll notify deployment team about this.

  36. David
    February 15, 2010 at 6:59 PM

    MacBook Pro 15″ running OS 10.6.2 (Snow Leopard).

    Safari 4.0.4
    Without JavaFX: 7.836sec
    Restart Browser (ie With JavaFX): 0.563sec
    Reload Page: 0.317sec

    Firefox 3.5.7 – Applet causes FireFox to hang (requires force quit)

    – David

  37. February 15, 2010 at 8:13 PM

    Thanks David.. The approach used for this evaluation uses Java – JavaScript bridge which may not be stable on Mac (due to previous version of JRE). I’ll try on Mac 10.6 and ‘ll get back to you..

  38. Galien
    February 15, 2010 at 10:27 PM

    Hi Rakesh, in ms

    IE8 64 bit:
    FireFox 3.6 32 bit

    OS=Vista 64bit
    cpu=intel i720
    hdd=sata 10k rpm

  39. David
    February 16, 2010 at 4:59 AM

    On the FireFox crash, I don’t think it’s your fault. I do applet development and I’ve been impressed with the progress made in Java 6 but applets still just ‘usually fail’ on common platforms. Mac + Firefox is one. I have a 10.5 and a 10.6 macbook… both fail to run applets more than half the time in FireFox but are usually fine in Safari… so I use FireFox for the web (I hate Safari) and Safari for development. Of course, since Safari isn’t popular, this means applets won’t be able to get serious market penetration on mac, which, as a dev, is worrying.

    – David

    • February 18, 2010 at 9:50 AM

      I use Mac 10.5 with FF 3.6, It looks stable with JRE 1.5.0_22. So would like to find if its issue with JRE or FF.. Is it for all Applets or specific to one using JavaScript/Media?

  1. February 9, 2010 at 10:27 AM
  2. February 15, 2010 at 10:16 AM

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: