-
Notifications
You must be signed in to change notification settings - Fork 729
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
Very slow startup on Windows Subsystem for Linux without -Xmx option #967
Comments
I tried to reproduce this issue on my Thinkpad using the most recent OpenJDK9+OpenJ9 build available from AdoptOpenJDK but everything runs ok for me:
As Peter Shipton hinted above, this could be related to GC trying to allocate the Java heap at a specified address, failing and then repeatedly trying with larger addresses in 4K increments. |
Thanks. I'll give it another spin. I haven't noticed any changes in OMR or OpenJ9 that might explain that better behavior. Maybe Microsoft fixed WSL? |
I downloaded the same version from adopt. Notice that most of the 26 seconds is before the first tracepoint: the time must be spent elsewhere.
An instance built on WSL has similar behavior.
|
A build based on eclipse-omr/omr#2743 seems much better (performance does not appear to be dependent on whether -Xmx is used nor the value used with that option).
|
I'm satisfied that this is fixed by eclipse-omr/omr#2743 which is now merged: closing. |
I built OpenJ9 using the Windows Subsytem for Linux available in Windows 10.
The output from
java -version
shows SHAs from today.There is a significant difference in runtime if the
-Xmx
option is present vs. omitted.It seems to be entirely in the initialization stage
ALL_LIBRARIES_LOADED
forj9gc29
.With
-Xmx4M
:Without
-Xmx
:The text was updated successfully, but these errors were encountered: