-
-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
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? Sign in to your account
Thread contention on Converters.PROPERTY_EDITOR #254
Comments
@raulcaj The classloader does cache by itself, indeed. Try doing some benchmark to verify. |
how did you verify that there is thread contention? I've not looked yet into it, but I know for sure that the classloader does caching. can you please elaborate your evidences about this? |
@lviggiano report |
also, I'd like to add that the result of isClassAvailable method should be cached too. |
ok then, sounds fine. If you want to send me a pull request I'll merge that. |
Great! I'll just finish running some more tests to see if I catch something else related to this and I'll create it. |
Thanks for the report; the improvement looks impressive. It's long time I'm not doing active development on this project, I need to cleanup two things, then I hope it won't take much time to release a new version on maven repository. Today afternoon I was fighting with maven+intellij since I was not using my laptop at home for development. |
Solves the thread contention problem reported on Issue #254
solved by #255 |
Hi!
There is a problem of thread contention on the PropertyEditorManager.findEditor. It loads classes from the ClassLoader switch is a thread blocking operation.
Is it possible to cache this method result so it wouldn't be called again or it would break this functionality somehow?
It would go something like this:
The text was updated successfully, but these errors were encountered: