ICU4J MessageFormat needs performance improvement

Description

Deleted Component: formatting

This is somewhat related to #7860, but I have a specific usage request. The typical usage scenario is to load a string from a resource bundle and cache nothing on the user end. When arguments are provided for the message look up, the looked up string is assumed to be used in a MessageFormat. Caching MessageFormat objects is not typical and not desirable in large projects nearing JVM memory limits.

We have reports that ICU4J MessageFormat is significantly slower than java.text.MessageFormat. This performance issue prevents us from using MessageFormat, especially in large formatted tables. The arguments are normally number, time and string types.

I can provide more specific examples upon request. They'll be similar to the tutorial I gave at a Unicode conference regarding the Eclipse externalize strings functionality.

Activity

Show:
TracBot
June 30, 2018, 11:31 PM
Trac Comment 2 by —2011-04-08T19:04:08.713Z

Hopefully performance will be better after ticket #8319 is implemented.

TracBot
June 30, 2018, 11:31 PM
Trac Comment 3 by —2011-04-23T00:07:50.860Z

Please provide examples – best would be an actual small perf test – and compare with ICU 4.8 (with the changes from ticket #8319).

Needs More Information

Assignee

Markus Scherer

Reporter

George Rhoten

Components

None

Labels

None

Reviewer

None

Priority

major

Time Needed

Hours

Fix versions