-
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
native-image memory usage higher in vm-21.2.0 compiled from source compared to the released binary #3697
Comments
@zakkak I have no idea what would be different, but if you find something I'm interested to hear what is going on. |
@zakkak You mention "Build native-image from source". How exactly are you building it? Specifically is this building libgraal native? |
The command I used to build from source is:
Good catch, no it doesn't! Building with:
does so, but I am still getting similar results. Enabling GC logs I see that the actual heap usage is not that different between the two builds, despite the consistent increased heap capacity in the case of the build-from-source GraalVM. GraalVM 21.2.0 built from source with native libgraal
GraalVM 21.2.0 downloaded from releases (with native libgraal as well)
. |
I am closing this, as it seems related to a slightly different allocation pattern that leads to the GC algorithm increasing the heap size a bit more aggressively in one of the two cases while the actual memory usage is not that different. |
Describe the issue
Looking into #3435 I tried compiling HelloWorld with
vm-21.2.0
downloaded from https://github.com/graalvm/graalvm-ce-builds/releases/tag/vm-21.2.0 and noticed thatnative-image
didn't use more memory than invm-21.1.0
. However, compilingvm-21.2.0
from source using:I can still observe increased memory usage.
How is this possible?
Comparing 10ff481 downloaded from https://github.com/graalvm/graalvm-ce-dev-builds/releases/tag/21.3.0-dev-20210817_2030 with 10ff481 built from source I don't see such a difference (both report 3.2GB)
Steps to reproduce the issue
Build
native-image
from source and compare memory usage to that of the correspondingnative-image
binary released upstream. (run multiple times to ensure the measurements are stable)For the measurements I compiled:
using
native-image HelloWorld
The text was updated successfully, but these errors were encountered: