There is significant performance regression when passing “-Djvmci.Compiler=graal” to jaotc.
Processing metadata time was increased from 58sec -> 1,397sec and total time was increased from 334sec -> 1,751sec.

Here are the results of running
“jaotc -J-Xmx4g --info -J-server -J-XX:+UnlockExperimentalVMOptions -J-XX:+EnableJVMCI -J-XX:+UseJVMCICompiler -J-Djvmci.Compiler=graal -J-ea -J-esa --compile-with-assertions --output libjdk.internal.vm.compiler.so --module jdk.internal.vm.compiler”

for jdk13-b11 promoted build and latest jdk13 bits:

jdk13-b11
19133 methods compiled, 85 methods failed (249127 ms)
Parsing compiled code (3546 ms)
Processing metadata (58332 ms)
Preparing stubs binary (1 ms)
Preparing compiled binary (206 ms)
Creating binary: ./tmp/libjdk.internal.vm.compiler.jit-graal.o (4970 ms)
Creating shared library: ./tmp/libjdk.internal.vm.compiler.jit-graal.so (3479 ms)
Total time: 334848 ms


jdk13-latest bits:
19568 methods compiled, 106 methods failed (324221 ms)
Parsing compiled code (3463 ms)
Processing metadata (1397645 ms)
Preparing stubs binary (4 ms)
Preparing compiled binary (197 ms)
Creating binary: ./tmp/libjdk.internal.vm.compiler.jit-graal.o (5343 ms)
Creating shared library: ./tmp/libjdk.internal.vm.compiler.jit-graal.so (3476 ms)
Total time: 1751079 ms

This performance regression seems came with JDK-8218074 “Update Graal”.