Question: What is the significance of the "-embvm-" attribute in a bundle name? For example:
Starting in the January 2021 PSU/CPU release cycle, Azul has introduced a number of new bundle configurations that contain "-embvm-" in the bundle name. This is primarily for Embedded customers.
In the past, certain bundles (eg. headless bundles for PPC, MIPS32, QNX, Arm, etc.) were created with this configuration, but were not clearly identified, so adding "-embvm-" was done to address that shortcoming. Additional bundle configurations (eg. cp1, cp2, cp3) have now also been created with the "-embvm-" configuration.
Internally, these bundles are created with a collection of build-time parameters used to build a light-weight, fast startup JVM.
If you are an embedded customer that have used headless PPC/MIPS32/QNX/ARM bundles, only the bundle name has changed.
If you are an embedded customer and have been provided with extra/new "-embvm-" bundles, feel free to ignore them or experiment with them to see if they provide you with any additional performance benefits.