Community
Participate
Working Groups
Eclipse 3.2 uses ICU4J 3.4.4.1. Duong ran a performance test against ICUs Collator vs java.text.Collator and found ICUs Collator to be 3.3 times slower. A bug has been logged against ICU4J: http://bugs.icu-project.org/cgi-bin/icu-bugs/incoming?findid=5174
Back to you for tracking Karice...
Some additional info. Seems the numbers vs 1.4 and 1.5 (both Sun) vary enough to be noted: Sun 1.5 IBM 1.5 java.Collator 54ms 162ms icu.Collator 360ms 516ms The numbers provided in the ICU bug were against IBM JDK 1.5. They were: java.text.Collator 157 com.ibm.icu.text.Collator 515
Just to clarify the test that I ran between the two Collator classes that I was only recording the start up time. Eg. Collator.getInstance()
*** Bug 170548 has been marked as a duplicate of this bug. ***
Looks like the ICU bug is targetted to be fixed in ICU4J 3.8, so Eclipse won't see this fix until post-3.3. http://bugs.icu-project.org/trac/ticket/5174
From the duplicate Bug 170548: This performance problem shows itself when first opening an editor in Eclipse. It takes up to 10 seconds on my older notebook and is really annoying.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.