bottleneck by java.lang.Class.getAnnotations()

[Alexander Knöller]

I know. But there is a usual solution to those kind of problems: double checked locking.
This would avoid synchronization for all the cases where no redefinitions take place.
(I also put in a bug-report for the sunjdk where I elaborated this a bit more.)
I am not so familiar with concurrency while using SoftReferences, but I guess using a local Variable for concurrency-avoidance for the annotations-field or the target of the SoftReference, then doing a nonsynchronized check for the redefinition and a potentially null-value on the local copy of the annotations-variable should suffice to decide that one could leave out the synced call and just returns the annotations-value (in the local variable)?

Also you would need to use a local variable while calculating the annotations-Field prior to assigning the result to the field to avoid concurrency-effects on the double-checked locking.

Since Code using getAnnotations() always could trap in an annotations-result not fitting any more to the class because of concurrent redefinition we would not need to take care of this (and the current code could cause this already inside "getAnnotations()".

-Alex

Am 01.11.2012 um 15:56 schrieb Joe Darcy:

> 
> On 11/1/2012 7:11 AM, Alan Bateman wrote:
>> On 01/11/2012 13:17, Alexander Knöller wrote:
>>> Hi there.
>>> 
>>> java.lang.Class.getAnnotations() always enters a synchronized-block, slowing down multi core machines that heavily make use of Annotations.
>>> (in our Case we use LoadTimeWeaving in the spring-framework 3.1.2)
>>> We are using sun-jdk 6 which has the same performance-bottleneck.
>>> openjdk7 and 8 show no fix so far, although it looks like it might be possible to build a kind of double-checked locking?
>>> 
>>> Has this issue ever been persued?
>>> 
>>> Special Regards
>>> Alex Knöller
>>> 
>> If you have a proposal then I suggest bringing it to core-libs-dev for discussion. In addition to contention there are other issues that need attention there too, particularly the potential to deadlock and the overhead per Class when annotations aren't used. There's definitely some useful work that could be done there.
>> 
>> 
> 
> Note that the block in question is synchronized so that getAnnotations returns the right result if the class has been redefined at runtime using an API for that purpose.
> 
> -Joe
>