id summary reporter owner description type status priority milestone component version severity resolution keywords cc 68 Performance of Java 6 is not too good Yoda_Java6 "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" defect closed major Next general 1.6.0-b19 Beta 2 medium wontfix