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.
#21271 Avoid repeated superclass introspection in AnnotationUtils.findAnnotation
#21508 Resolved ApplicationListener event type should get cached
#21840 Unnecessary sort in AbstractApplicationEventMulticaster