-
Bug
-
Resolution: Fixed
-
P4
-
1.4.2
-
05
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2072983 | 5.0 | Iris Clark | P4 | Resolved | Fixed | b28 |
Repeated calls to Class.getName() have become a major bottleneck for a number of key applictions. The biggest issue is with spidermark, a web services benchmark: JAXB processing in spidermark makes heavy use of Proxy classes, which in turn make repeated calls to Class.getName(); spidermark spends 30% of its time in that method. The SunOne application server also has this issue because it uses Method objects in a number of hashtables, and the hashCode() method of the Method class contains 2 calls to Class.getName() -- accounting for 4% of the time spent running SPECjAppServer.
This needs to be addressed for 1.4.2_03 and for 1.5.
This needs to be addressed for 1.4.2_03 and for 1.5.
- backported by
-
JDK-2072983 (reflect) Class.getName() is a major performance bottleneck
- Resolved
- relates to
-
JDK-5058117 (reflect) inefficient methods in java.lang.Class due to non-cached natives
- Open
-
JDK-5018965 (reflect) Class.getName() calls String.intern() twice
- Resolved
-
JDK-8187123 (reflect) Class#getCanonicalName and Class#getSimpleName is a part of performance issue
- Resolved