Skip to content

I think, this command is correct. "time java -XX:+UnlockExperimentalVMOptions -XX:+UseJVMCICompiler TopTen large.txt" #6

@Revolution2021

Description

@Revolution2021

Sorry, one more question.
In the article(https://medium.com/graalvm/graalvm-ten-things-12d9111f307d ), the following is written.

>To run without the GraalVM JIT compiler to compare, I can use the flag -XX:-UseJVMCICompiler. JVMCI is the interface between GraalVM and the JVM. You could also compare against your standard JVM as well.

However, in my environment, it doesn't work.

root@taro123:/opt/graalvm-ce-java11-21.3.0/graalvm-ten-things# time java -XX:-UseJVMCICompiler TopTen large.txt
Error: VM option 'UseJVMCICompiler' is experimental and must be enabled via -XX:+UnlockExperimentalVMOptions.
Error: The unlock option must precede 'UseJVMCICompiler'.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

real    0m0.008s
user    0m0.001s
sys     0m0.007s

I think, the below is correct.
** time java -XX:+UnlockExperimentalVMOptions -XX:+UseJVMCICompiler TopTen large.txt **

The below is the successful result for your reference.
Is that just a mistake or caused by my environment , GraalVM(CE) + Ubuntu20?

root@taro123:/opt/graalvm-ce-java11-21.3.0/graalvm-ten-things# time java -XX:+UnlockExperimentalVMOptions -XX:+UseJVMCICompiler TopTen large.txt
sed = 502500
ut = 392500
in = 377500
et = 352500
id = 317500
eu = 317500
eget = 302500
vel = 300000
a = 287500
sit = 282500

real    0m26.024s
user    0m37.151s
sys     0m1.121s

Regards,

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions