Investigation into traces of J2SE startup time has shown that
sun.io.CharacterEncoding spends roughly 60 milliseconds during core
libraries startup performing roughly 700 HashMap.put() operations
mapping the name of an encoding to the name of the byte-to-character
converter used for that encoding. At least the common US-ASCII case
should be done up front and most of these calls avoided.
sun.io.CharacterEncoding spends roughly 60 milliseconds during core
libraries startup performing roughly 700 HashMap.put() operations
mapping the name of an encoding to the name of the byte-to-character
converter used for that encoding. At least the common US-ASCII case
should be done up front and most of these calls avoided.
- relates to
-
JDK-4759354 Locale 'ru_RU.CP1251' is not supported
-
- Closed
-
-
JDK-4757212 JVM 1.4.2 regression on Sierra EE startup compared to JVM 1.3.1 in mixed mode
-
- Closed
-