The primary goal of JDK-8356447 was to have initialization of the Graal JIT occur in the same phase as the rest of VM startup such that initialization problems are detected and reported prior to executing any user code.

This change caused a performance regression for Truffle when it is being used in a JDK build that includes both jargraal and libgraal. The problem is that Truffle needs to use (and thus initialize) jarjvmci but it does not need jargraal for compilation (libgraal is used). With EagerJVMCI now defaulting to true, it means that jargraal is unnecessarily initialized as part of initializing jarjvmci. The solution is to make EagerJVMCI only apply to the JVMCI runtime used by HotSpot's CompileBroker.