JDK-4747362 : Optimize CharacterEncoding for US-ASCII
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-09-13
  • Updated: 2002-11-11
  • Resolved: 2002-10-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 mantisFixed
Related Reports
Relates :  
Relates :  
Description
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.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b05 VERIFIED IN: mantis
14-06-2004

WORK AROUND
11-06-2004

SUGGESTED FIX
11-06-2004

PUBLIC COMMENTS
10-06-2004

EVALUATION Implementing this eliminates this method from the call trace. At most a few other common encodings should be placed in the table up front. Implemented in 1.4.2. ###@###.### 2002-09-13 ###@###.### has provided the additional common-case encodings. ###@###.### 2002-10-01
13-09-2002