Put this on maven central so that openjdk users can use graal.js #17

markehammons · 2018-06-13T10:35:01Z

Right now, maven central has 2 of 4 jars needed to run graal.js on non-graalvm jdks. Graal-sdk, and truffle api. Tregex and graal.js.jar should me published to maven central as well so people can start testing running the polyglot engine and graal.js on non-graal vm jdks. I've tested this setup works by ripping the graal.js and tregex from a graalvm ce 1.0.0-rc2 release and putting them on the classpath with the graal-sdk and truffle api jars.

wirthi · 2018-06-13T10:59:11Z

Hi Mark,

we are a bit careful with that approach. Yes, it does work - but we do not recommend it, as performance is far off of what you get when running on GraalVM itself. This problem might be resolved in future versions of JVM; we are working with the Oracle JVM team so that future JVM versions will have the relevant support built-in already, and you just need the respective .jar file of the language you want to use.

We'll discuss internally how to better distribute until then.

eliasvasylenko · 2018-06-15T09:42:33Z

Just to add another data point here, there are definitely users out there who don't care that much about performance or AOT and would just like access to all the convenient interop stuff on a stock JVM.

(Also I've been struggling to find information about what the differences actually are between GraalVM and the JVM. Graal can be used as the JIT compiler on a normal JVM via JVMCI, right? I'm confused as to what else is involved that means the performance is still "far off" from the GraalVM, is there any documentation which goes over this?)

dougxc · 2018-06-15T09:52:14Z

The version of Graal in the stock JDK does not (currently) include Truffle partial evaluation. For example:

> jar tf /Library/Java/JavaVirtualMachines/graalvm-ee-1.0.0-rc2/Contents/Home/jre/lib/jvmci/graal.jar | grep truffle | wc -l
     256
> /Library/Java/JavaVirtualMachines/jdk-10.jdk/Contents/Home/bin/jmod list /Library/Java/JavaVirtualMachines/jdk-10.jdk/Contents/Home/jmods/jdk.internal.vm.compiler.jmod  | grep truffle | wc -l
       0

eliasvasylenko · 2018-06-15T09:57:36Z

Ah I understand, thanks.

StephenOTT · 2018-07-11T15:04:31Z

+1 for this functionality 💯

jonnermut · 2018-09-18T12:25:24Z

we are a bit careful with that approach. Yes, it does work - but we do not recommend it, as performance is far off of what you get when running on GraalVM itself. This problem might be resolved in future versions of JVM; we are working with the Oracle JVM team so that future JVM versions will have the relevant support built-in already, and you just need the respective .jar file of the language you want to use.

We'll discuss internally how to better distribute until then.

Are there any metrics available on performance without GraalVM? Is it better/same/worse than Nashorn is probably the key one...
Does any of this (running GraalJS on a normal JDK) change with Java 11?
I'm interested in GraalJS as an upgrade for Nashorn - given it's deprecated any never going to get ES6+/Node.js features.

wirthi · 2018-09-18T12:44:24Z

@jonnermut without Graal (Graal, the Java JIT compiler), there is no special optimization of the Graal JavaScript interpreter. No partial evaluation (as with Graal), no bytecode generation (as with Nashorn). Performance characteristics are those of an interpreter than, definitly worse on peak performance.

On JDK11+ it will be possible to execute Graal.js with Graal as JIT compiler by setting a few JVM flags. Performance will then be identical to using our custom-built GraalVM.

jonnermut · 2018-09-25T03:51:31Z

Thanks for the explanation @wirthi
Is there any doco yet on how to use Graal.js with JDK 11? We'll still need to manually add the Graal.js jar and its dependencies?

jGauravGupta · 2018-09-27T14:24:01Z

+1 for tregex, graaljs and graaljs-scriptengine

rsalvador · 2018-10-09T10:57:32Z

On JDK11+ it will be possible to execute Graal.js with Graal as JIT compiler by setting a few JVM flags

@wirthi what are the JVM flags to set?.
We are trying Graal.js with http://jdk.java.net/11 (macos) but is running in interpreter mode.

greensopinion · 2018-10-17T20:36:28Z

I'm with @eliasvasylenko - I'm interested in running JavaScript on a JVM, regardless of performance.
At the moment we're just interested in evaluating Graal as an alternative to Nashorn for our existing Java application that runs JavaScript extensions.

Is it just a matter of getting the two missing jars (which aren't published to Maven Central?) and adding them to the classpath?
If that's the case, and if performance becomes a concern, we could look at using the Graal JIT compiler as a future option.

greensopinion · 2018-10-17T20:58:25Z

In case it helps anyone else, here's what I did that got me off the ground:

download the GrallVM SDK
add jre/tools/regex/tregex.jar and jre/languages/js/graaljs.jar from the download to the classpath of a Maven project
add truffle-api and graal-sdk as Maven dependencies (same version as the downloaded SDK)
compile/run using org.graalvm.polyglot.Context and related Java APIs

I don't know if that's complete, but it's sufficient to run a trivial JavaScript on a JVM from a Java program, with performance caveats per above.

woess · 2018-10-19T01:39:36Z

We plan to publish all the necessary artifacts for running on JDK 11 (with additional JVM flags) to Maven Central in the near future. Stay tuned.

zzFluke · 2018-12-11T10:52:34Z

We plan to publish all the necessary artifacts for running on JDK 11 (with additional JVM flags) to Maven Central in the near future. Stay tuned.

Hi Andreas, I wonder is there any updates on publishing? Is there some ETA when this is going to be done? Thank you very much!

rsalvador · 2018-12-11T11:43:25Z

@zzFluke the artifacts are already in maven central, the rc8 release notes have instructions on how to use them: https://www.graalvm.org/docs/release-notes/#10-rc8
See also this example project: https://github.com/graalvm/graal-js-jdk11-maven-demo

zzFluke · 2018-12-17T16:19:39Z

Many thanks @rsalvador !!! I'm going to give it a try.

zimmi · 2019-02-20T11:36:58Z

Edit: See #17 (comment) for official benchmarks, the measurements below were done on an old laptop running other software just to get a general idea, so they are probably not very accurate.

For future reference, to set some very rough performance expectations:

Running the example project with graal.js version 1.0.0-rc12 on openjdk 11.0.2 with a dated Intel i5-3210M (4) @ 3.100GHz: Without adding command line flags, graal.js is ~5x slower than Nashorn.
Adding command line flags makes it ~3x faster than Nashorn. Using ScriptEngine vs Context did not have a huge impact.

zzFluke · 2019-02-20T13:35:46Z

For future reference, to set some very rough performance expectations:

Running the example project with graal.js version 1.0.0-rc12 on openjdk 11.0.2 with a dated Intel i5-3210M (4) @ 3.100GHz: Without adding command line flags, graal.js is ~5x slower than Nashorn.
Adding command line flags makes it ~3x faster than Nashorn. Using ScriptEngine vs Context did not have a huge impact.

@zimmi, may I wonder which flags did you mean?

zimmi · 2019-02-20T18:34:05Z

@zzFluke

I ran mvn clean package inside the example project, which runs all benchmarks. Looking at the pom.xml, this adds the following flags: -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI --module-path=${compiler.dir} --upgrade-module-path=${compiler.dir}/compiler.jar. To run the benchmarks without the flags, I just commented out that section in the pom.

${compiler.dir} contains org.graalvm.compiler:compiler, org.graalvm.truffle:truffle-api and org.graalvm.sdk:graal-sdk.

wirthi · 2019-02-22T11:30:15Z

Hi @zimmi, Hi @zzFluke

thanks for your investigations. We have just published a blog post to bring more clarity into this and present it more officially.

https://medium.com/graalvm/graalvms-javascript-engine-on-jdk11-with-high-performance-3e79f968a819

Thanks,
Christian

plata · 2019-03-02T17:17:26Z

I'm trying to create a ScriptEngine with "graal.js" however, I always get null (see reference above). Any hints what might be wrong?

EDIT: Nevermind, I think I've messed up my Maven dependencies...

wirthi · 2019-03-05T09:32:20Z

Hi @plata

what setup are you using? Do you start from JDK11 as in the blogpost, or are you on one of our GraalVM builds? On GraalVM, I don't see any obvious reason why that should not work (if so, can you please post a minimal example of your code and commands to start). On JDK11 or any other setup where you provide the JARs yourself, the most obvious thing missing could be the jars for js-scriptengine. If you start from our demo application (https://github.com/graalvm/graal-js-jdk11-maven-demo) as described in the blogpost, that should not happen. Again, if this still fails, please post your source code and command lines, then we might be able to help you.

Thanks,
Christian

plata · 2019-03-05T10:06:57Z

Like I said, I've found my error in the meantime (I had added the dependencies to dependenyManagement in Maven...). Nevertheless, thanks for your response.

ispringer · 2024-02-01T17:46:18Z

What are the Maven artifacts that need to be included for GraalVM JDK17? I do not see anything in the docs. I tried including the same jars we did for JDK11, and I'm getting the following exception at runtime:

Caused by: org.graalvm.polyglot.PolyglotException: java.lang.NoClassDefFoundError: com/ibm/icu/text/DateFormat
	at com.oracle.truffle.js.runtime.JSContextOptions.<clinit>(JSContextOptions.java:454)
	at com.oracle.truffle.js.lang.JavaScriptLanguage.<clinit>(JavaScriptLanguage.java:180)
	at com.oracle.truffle.js.lang.JavaScriptLanguageProvider.create(JavaScriptLanguageProvider.java:51)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.LanguageCache.loadLanguage(LanguageCache.java:567)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotLanguageInstance.<init>(PolyglotLanguageInstance.java:100)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotLanguage.getInitLanguage(PolyglotLanguage.java:154)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotLanguage.ensureInitialized(PolyglotLanguage.java:144)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotLanguage.getOptionsInternal(PolyglotLanguage.java:136)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotLanguage.getOptionValues(PolyglotLanguage.java:204)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotEngineImpl.<init>(PolyglotEngineImpl.java:325)
	at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotImpl.buildEngine(PolyglotImpl.java:286)
	at org.graalvm.sdk/org.graalvm.polyglot.Engine$Builder.build(Engine.java:681)

It would be really helpful if an example Maven project like https://github.com/graalvm/graal-js-jdk11-maven-demo was included for JDK17 and JDK21 as well.

ispringer · 2024-02-02T02:51:52Z

It looks like the reason for ICU4J being missing is that I installed the js language pack manually using jar xvf, rather than via gu install.

[ianspri-ltmw2bn:~]$ gu install -L -D ~/Downloads/js-installable-svm-java17-darwin-aarch64-23.0.2.jar
Processing Component archive: /Users/ian.springer/Downloads/js-installable-svm-java17-darwin-aarch64-23.0.2.jar
Missing required component(s):
    org.graalvm.icu4j, required by: Graal.js (org.graalvm.js)
    org.graalvm.regex, required by: Graal.js (org.graalvm.js)
Error: There were unresolved dependencies, terminating installation.

The reason I did this was because gu install failed on Amazon Linux due to this bug: oracle/graal#7951

woess · 2024-02-02T23:06:02Z

@ispringer It seems you're using an older version of GraalVM. There's no gu in 23.1+ anymore. Rather, we put all our language jars on Maven now, exactly as this issue requested. We blogged about this change here: https://medium.com/graalvm/truffle-unchained-13887b77b62c

Ideally, you should be able to pull in JS into your Maven project using:

<dependency> 
    <groupId>org.graalvm.polyglot</groupId> 
    <artifactId>polyglot</artifactId> 
    <version>23.1.2</version> 
</dependency>
<dependency> 
    <groupId>org.graalvm.polyglot</groupId>
    <artifactId>js</artifactId> <!-- or js-community -->
    <version>23.1.2</version> 
    <type>pom</type>
</dependency>

and run it on a recent GraalVM for JDK 21.

wirthi assigned wirthi and ansalond Jun 13, 2018

oobles mentioned this issue Jul 16, 2018

Build steps for embedding graalvm oracle/graal#550

Closed

jGauravGupta mentioned this issue Sep 29, 2018

Nashorn engine to GraalJS migration jeddict/jeddict#294

Closed

boris-spas closed this as completed Jan 8, 2019

plata mentioned this issue Mar 2, 2019

Allow to create graal.js engine in PhoenicisScriptEngineFactory PhoenicisOrg/phoenicis#1872

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Put this on maven central so that openjdk users can use graal.js #17

Put this on maven central so that openjdk users can use graal.js #17

markehammons commented Jun 13, 2018 •

edited

Loading

wirthi commented Jun 13, 2018

eliasvasylenko commented Jun 15, 2018

dougxc commented Jun 15, 2018

eliasvasylenko commented Jun 15, 2018

StephenOTT commented Jul 11, 2018 •

edited

Loading

jonnermut commented Sep 18, 2018 •

edited

Loading

wirthi commented Sep 18, 2018

jonnermut commented Sep 25, 2018 •

edited

Loading

jGauravGupta commented Sep 27, 2018

rsalvador commented Oct 9, 2018

greensopinion commented Oct 17, 2018

greensopinion commented Oct 17, 2018

woess commented Oct 19, 2018

zzFluke commented Dec 11, 2018

rsalvador commented Dec 11, 2018 •

edited

Loading

zzFluke commented Dec 17, 2018 •

edited

Loading

zimmi commented Feb 20, 2019 •

edited

Loading

zzFluke commented Feb 20, 2019

zimmi commented Feb 20, 2019

wirthi commented Feb 22, 2019

plata commented Mar 2, 2019 •

edited

Loading

wirthi commented Mar 5, 2019

plata commented Mar 5, 2019

ispringer commented Feb 1, 2024 •

edited

Loading

ispringer commented Feb 2, 2024

woess commented Feb 2, 2024 •

edited

Loading

Put this on maven central so that openjdk users can use graal.js #17

Put this on maven central so that openjdk users can use graal.js #17

Comments

markehammons commented Jun 13, 2018 • edited Loading

wirthi commented Jun 13, 2018

eliasvasylenko commented Jun 15, 2018

dougxc commented Jun 15, 2018

eliasvasylenko commented Jun 15, 2018

StephenOTT commented Jul 11, 2018 • edited Loading

jonnermut commented Sep 18, 2018 • edited Loading

wirthi commented Sep 18, 2018

jonnermut commented Sep 25, 2018 • edited Loading

jGauravGupta commented Sep 27, 2018

rsalvador commented Oct 9, 2018

greensopinion commented Oct 17, 2018

greensopinion commented Oct 17, 2018

woess commented Oct 19, 2018

zzFluke commented Dec 11, 2018

rsalvador commented Dec 11, 2018 • edited Loading

zzFluke commented Dec 17, 2018 • edited Loading

zimmi commented Feb 20, 2019 • edited Loading

zzFluke commented Feb 20, 2019

zimmi commented Feb 20, 2019

wirthi commented Feb 22, 2019

plata commented Mar 2, 2019 • edited Loading

wirthi commented Mar 5, 2019

plata commented Mar 5, 2019

ispringer commented Feb 1, 2024 • edited Loading

ispringer commented Feb 2, 2024

woess commented Feb 2, 2024 • edited Loading

markehammons commented Jun 13, 2018 •

edited

Loading

StephenOTT commented Jul 11, 2018 •

edited

Loading

jonnermut commented Sep 18, 2018 •

edited

Loading

jonnermut commented Sep 25, 2018 •

edited

Loading

rsalvador commented Dec 11, 2018 •

edited

Loading

zzFluke commented Dec 17, 2018 •

edited

Loading

zimmi commented Feb 20, 2019 •

edited

Loading

plata commented Mar 2, 2019 •

edited

Loading

ispringer commented Feb 1, 2024 •

edited

Loading

woess commented Feb 2, 2024 •

edited

Loading