-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Executable size regression in 21.1 #3280
Comments
@kirillp please provide the reproducer |
What is not clear? |
I assume this is reproducible with the hello world:
@kirillp please confirm if that's the case, thank you. |
Right, the issue here is that we see +500k grow in executable size |
FWIW - there's a similar discussion going on right now related to this here #3422. I see that you created this issue on 15 March and were using 21.1.0.dev version. The commit/change which is being discussed in the other issue was done on March 10, so it's likely that what you are seeing here is the same as what's being discussed in that other issue. |
I see a 3MB increase when upgrading babashka to 21.1.0. The diff shows that classes from used_classes_bb_20210522_140854_21.0.0.txt |
Closing this older ticket. Note we now have the -Os argument to optimize for size, if that is your main pain point. https://www.graalvm.org/jdk23/reference-manual/native-image/guides/optimize-for-file-size/ |
Describe the issue
My simple app compiled by graalvm-ce-java11-21.0.0 is 7500k executable
And if compiled by graalvm-ce-java11-21.1.0-dev - 8M executable
So executable is 500k size bigger, have no differences in source code.
Steps to reproduce the issue
Please include both build steps as well as run steps
Use trivial System.out.println(); program
Compile it using graalvm-ce-java11-21.0.0 and graalvm-ce-java11-21.1.0-dev
Describe GraalVM and your environment:
GraalVM version
GRAALVM_VERSION="21.1.0-dev" JAVA_VERSION_DATE="2021-01-19"
GRAALVM_VERSION="21.0.0" JAVA_VERSION="11.0.10"
JDK major version: 11
OS: Windows
Architecture: AMD64
The text was updated successfully, but these errors were encountered: