SHORT SUMMARY: REGRESSION: POOR TIMEZONE.GETDEFAULT() PERFORMANCE DUE TO
SYNCHRONIZATION
INDICATORS: Slow performance on applications making heavy use of
TimeZone.getDefault()
COUNTER INDICATORS: N/A
TRIGGERS:
Performance issue due to heavy synchonization around TimeZone.getDefault()
Seen if many threads contend for same monitor lock.
KNOWN WORKAROUND: N/A
PRESENT SINCE: 6u31, 7u3
HOW TO VERIFY: Testcase supplied in BugDB report
NOTES FOR SE:
Investigate current sychonization logic in TimeZone.getDefault() methods (and
resulting
call chain) and determine whether the proposed solution in BugDB report is
viable.
REGRESSION: Since 6u31, 7u3
Introduced at time of http://monaco.sfbay.sun.com/detail.jsf?cr=7110687
http://jpsesvr.us.oracle.com:8080/ctetools/html/SingleReview.jsp?index=4328
|