Custom Query (172 matches)

Java 6 still feels a quite a bit slow (in some areas). To demonstrate it, I used Jeti/2, measuring time from starting it and until GUI is up and roster and 4 MUCs (2 on local server 2 on remote) are populated.

All tests done from same client PC, only the loaded Java versions are different.

Jabber server Java 6 on eCS

Time to start Jeti/2 until roster and 4 MUC are filled

Java 1.41 | Java 1.42 | Java 1.50 | Java 1.60 |

| | | |

9 secs | 20 secs | 45 secs | 35 secs | 9 secs | 15 secs | 35 secs | 25 secs | 9 secs | 25 secs | 38 secs | 33 secs | 9 secs | 16 secs | 30 secs | 24 secs |

| | | |

1) 2) 3) 4)

(A lot more tests was actually done - these are the best results)

1) Java 1.41 loads in 9 secs in almost every test done.

2) Between 15-25 secs in mosts test. Not easy to see any specific

slow part.

3) Has seems to have some timing issues with sockets / DNS - hang

for a long time in same place.

4) Lots of tests were over 1 minut to load. Splash screen is

visible slowly drawn in parts. Communication with server seems to take a long time.

There seems to be room for improvement - although it may be hard to compete with our native 1.41

Java includes a dependence on ​ftp://ftp.netlabs.org/pub/gcc/gcc4core.wpi. This can result in multiple installs of these DLLs, wasted bandwidth downloading them yet again for very little benefit. Simple solution is to set GCCOPT='-static-libgcc' This will statically link the couple of small functions that may be needed.

After certain testing TVBrowser (3.0 RC3) (​http://www.tvbrowser.org/) works so far. Unfortunately the settings window do not appear in the correct size. Control-buttons (like "OK") are only visible after window resize by hand. This bug is probably not related to RC-Status of TVBrowser. It does not occur under WinXP-Java. See also the attached pictures.