Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Rahul Shinde opened SPR-17343 and commented
While benchmarking an application that has more than 10K+ beans, around 8 - 10 seconds was spent in identifying just the EventListener candidates during startup.
Since we have the information for EventListener implementations beforehand, would like to provide that to avoid introspection of all other beans in the registry.
Applications can then extend EventListenerMethodProcessor and provide their own implementation that specifies subset of bean names to inspect.
Affects: 5.0.9, 5.1 GA
Referenced from: pull request #1980
The text was updated successfully, but these errors were encountered:
Stéphane Nicoll commented
Juergen Hoeller I wonder if the component index couldn't be extended to pre-compute that information. Rather than providing a hook point, we could redirect this project to use the index (10K is quite a lot)
Sorry, something went wrong.
Duplicate of #1980
No branches or pull requests