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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native image size increased substantially with version 20.1 #2756
Comments
One clarification: The windows image size is still only 39MB. This appears to be a Linux/MacOS issue. |
Can we provide any additional information or otherwise help with resolve this? npm download size is a significant concern when we start talking about 100s of MB for each supported platform. |
This problem still exists with version 20.2.0 |
Is it possible to get confirmation that this is expected for Graal Native image 20+? |
I built an image from |
@cstancu I just build GraalVM from master/source on my Mac. The native image produced was 216MB. What JDK were you using? |
Or perhaps there are default compilation options or environment variables getting you much better results? Using the GraalVM Dashboard the size inflation is all coming from the heap - specifically |
Describe the issue
馃憢 We've been using native-image generation for quite some time with Closure-Compiler. I recently upgraded from version 19.0.0 to 20.1.0. The images generated by Graal increased in size by an order of magnitude when I did that.
19.0.0 - Java 8:
compiler.jar: 8,607,558 bytes
native-image on MacOS: 36,693,476 bytes (other OSs are similar size)
20.1.0 - Java 8:
compiler.jar: 8,607,558 bytes
native-image on MacOS: over 180 MB (other OSs are similar size)
Now I'm upgrading from Java 8 to Java 11 and getting even larger images:
20.1.0 - Java 11:
native-image on MacOS: over 270 MB (other OSs are similar size)
I tried looking through compiler options, but nothing stood out that would contribute to the size increase so significantly
Steps to reproduce the issue
Please include both build steps as well as run steps
Describe GraalVM and your environment:
More details
The text was updated successfully, but these errors were encountered: