Closed
Description
Juergen Hoeller opened SPR-17064 and commented
As a follow-up to #21271, it turns out that AnnotationAwareOrderComparator
can become a hotspot. Caching annotation-derived order results per Class
, ideally at OrderUtils
level, should provide significant benefits in scenarios with repeated sort attempts.
Affects: 5.0.6
Issue Links:
- Avoid repeated superclass introspection in AnnotationUtils.findAnnotation [SPR-16730] #21271 Avoid repeated superclass introspection in AnnotationUtils.findAnnotation
- Resolved ApplicationListener event type should get cached [SPR-16970] #21508 Resolved ApplicationListener event type should get cached
- Unnecessary sort in AbstractApplicationEventMulticaster [SPR-17307] #21840 Unnecessary sort in AbstractApplicationEventMulticaster