Bug ID: JDK-4911220 Reduce loading time for awt resources

Type: Bug
Component: client-libs
Sub-Component: java.awt
Affected Version: 6

Priority: P3
Status: Closed
Resolution: Won't Fix
OS: windows_nt
CPU: x86

Submitted: 2003-08-22
Updated: 2013-11-01
Resolved: 2005-07-29

In a recent startup performance analysis, the call to 
getBundle("sun.awt.resources.awt") appeared to take about 7% of the
total time in starting a simple AWT application.  Most of the work
here boiled down into several expensive calls relating to ClassPath
access and Files:
- URLClassPath.getLoader is called several times at nearly 10 ms per time
- Launcher.getFileURL is called several times at about 3 ms per time
- various other String and File calls are made many times.  While individually
inexpensive, these calls add up in the long run.

EVALUATION I ran a simple GUI application and I found the time to get the awt resources is now decrease to only 2-3% of the whole start up time (time to main). So with the work of 6280517, the performance of getting resources has been increased, at least for Awt and Swing resources.
29-07-2005
EVALUATION Comment from ###@###.###: This should be a general issue for resource bundle loading and I think my fix of using ResourceBundle.Control will definitely relieve the situation. But in general, I don't think we could fix the URLClassPath etc. So I think you should close it as "Will Not Fix" since there is no way we could fix the URLClassPath stuff. End of comment. So I close this bug as will not fix.
29-07-2005
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
21-08-2004
EVALUATION Should try to fix this for Tiger. ###@###.### 2003-08-22 4881291 should help out with this, too. ###@###.### 2003-10-24 Performance (startup) is a driver for Mustang, should investigate. ###@###.### 2005-05-26 11:36:02 GMT
24-10-2003