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
Set OptimizedAccessorFactory.noOptimization=true by default #1525
Conversation
Signed-off-by: Jim Ma <ema@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What problem on which JDK is this trying to resolve? In all cases I've seen on JDK 11+ so far was that the caller did not support multi-release jar files (ie Ant <=1.10.6); in such case using -Djdk.util.jar.enableMultiRelease=force
is the way to go
@lukasj I see there is a huge performance decrease in jaxb 2.3.3 with jdk8 with this default value |
Since JDK 9, this is off by default (noOptimization is true). Can you share a testcase showing the decrease on JDK8? |
@lukasj Can you please point me the source code to set this off (noOptimazation is true) by default since JDK9 ? |
see the Injector which does nothing and is supposed to be used |
Thanks @lukasj .
I pushed the test case project for the performance issue with JDK8: https://github.com/jimma/jaxb233perfmance . The steps to reproduce this issue are listed on README. Please check. |
@lukasj Did you get time to look at the producer ? The optimization change in jaxb 2.3.3. makes creates JAXBContext instance 10 times slower than jaxb 2.3.2. |
yup, you're right. Anyway, correct way to fix it is to just remove the code completely instead of setting variable to |
superseded by #1533 |
No description provided.