The memory options work for Native Image as well (I believe - at least seem to), and are useful so would be better to have these as separate options.

The memory options work for Native Image as well (I believe - at least seem to), and are useful so would be better to have these as separate options.

How do you set memory options work for Native Image?

Btw. I've noticed that ENSO_JVM_OPTS are used as enso executable arguments when launching native image enso executable. If that's what you are referring to @jdunkerley, then that's pretty dangerous - that means (with the expected introduction of JVM/NI switch in package.yaml) that the ENSO_JVM_OPTS change their interpretation when changing JVM/NI mode.

That's quite confusing and it will have to be changed anyway.

I'm not really convinced about this change. People tend to set their options globally or reuse them in various scripts. So this can cause more harm than good by leading to some unexpected behaviour. I'd rather we make this explicit.

• setting ENSO_JVM_OPTS is explicit
• I don't expect any of the Enso target audience users to have ENSO_JVM_OPTS set. Am I wrong?
• moreover as pointed out here the meaning of ENSO_JVM_OPTS changes currently - which makes little sense
• ENSO_JVM_OPTS are JVM options - e.g. they should be applied only to JVM mode.
• as such I don't think Enso users would be seeing anything unexpected

Some of our users are using this flag as it is what we have provided so far - we can provide an alternative to adjust the memory settings which would allow us more control.

Some of our users are using this flag as it is what we have provided so far

With the change in this PR such users should see (completely) compatible behavior. If they have ENSO_JVM_OPTS for example to increase memory, the memory will continue to be increased as we launch in JVM mode and apply exactly the same settings.

we can provide an alternative to adjust the memory settings which would allow us more control.

The GraalVM Launcher API differentiates between --vm.xyz option and --jvm.xyz option. The former one is applied to both modes (native one as well as JVM one). Usage of the latter turns on the JVM mode and applies both vm and jvm options.

Such a scheme is standard for all GraalVM language launchers and we should mimic it. We couldn't do it so far, as the scheme only works if the native mode is the default one. A bit more investigation into behavior of the GraalVM launchers is needed as we aren't directly using the launcher infrastructure ...

• Align Enso launcher with Truffle's AbstractLanguageLauncher #10335 (comment)

... just trying to mimic it ourselves.

Nightly release CI run scheduled.

• after downloading and unzipping
• and executing ./enso-linux-x86_64-2025.1.1-nightly.2025.3.17.1.AppImage --no-sandbox
• there still is Running Language Server in JVM mode
• e.g. the change in this PR doesn't seem to work

Not sure where exactly the problem is. When I do:

$ ./enso-linux-x86_64-2025.1.1-nightly.2025.3.17.1.AppImage --appimage-extract
$ ls -l squashfs-root/resources/enso/dist/2025.1.1-nightly.2025.3.17.1/bin/enso -h
-rwxr-xr-x 1 devel devel 480M bře 17 11:30 squashfs-root/resources/enso/dist/2025.1.1-nightly.2025.3.17.1/bin/enso

e.g. the enso native image binary is present in the AppImage.

How do you set memory options work for Native Image?

James has just provided a link to https://www.graalvm.org/latest/reference-manual/native-image/optimizations-and-performance/MemoryManagement/#java-heap-size

The memory options work for Native Image as well

Thus I assume following example is the way to set memory options work for Native Image with 2025.1.1-nightly.2025.3.17:

enso$ export ENSO_LAUNCHER=native
enso$ export ENSO_JVM_OPTS=-Xms2m -Xmx10m -Xmn1m
enso$ ./project-manager

The above then launches enso in native image mode and provides memory settings to it. Such a scenario will not work anymore with this PR - with this PR the above would launch enso in JVM mode and pass the memory settings to the JVM.

Closing unmerged as:

• there is no support for turning on memory settings in native image mode
• the built AppImage is still launching in JVM mode