-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Performance issues with SerializableTypeWrapper on Java 1.7.0_51 [SPR-11335] #15959
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
Comments
Phil Webb commented
|
Torsten Krah commented We are seeing this too, test times are ridiculous now with 1.7.0_51 - 1.7.0_45 is fine. |
Phil Webb commented Torsten Krah, I have just pushed a fix to master. We are seeing improvements locally with the Spring XD build but it would be good if you could try the latest snapshots (when build 723 https://build.springsource.org/browse/SPR-PUB-723 finishes) and let us know if it also works for you. |
Torsten Krah commented Hi Phil, thanks for the update, fix is working for us too. |
Phil Webb commented Great! Thanks for testing :) |
Gary Russell commented A heads up that this also fixes a Spring Integration issue with 7u51 where the conversion service failed to convert a [Map of Maps of Collections of Foo] to a [Map of Maps of Collections of Bar] (where a FooToBar converter is registered). This test 1 works with Spring 4.0.0 and 7u45, is broken with 4.0.0 and 7u51, and fixed with 4.0.1.BUILD-SNAPSHOT. |
Phil Webb commented Cheers Gary! |
Charles O'Farrell commented In addition to just performance we (Atlassian Stash) saw a memory leak (#16021) when the same proxied object was added to the Just mentioning that here for completeness (I had to spend a while tracking down the exact commit that fixed it). |
Phil Webb opened SPR-11335 and commented
The Spring XD build time jumped from 7mins to over 20mins following a Java upgrade to 1.7.0_51.
The root cause of the performance problems appears to be
SerializableTypeWrapper
.Referenced from: commits d96b91a
2 votes, 6 watchers
The text was updated successfully, but these errors were encountered: