Key

This line was added.

This line was removed.

Formatting was changed.

Running The Octane microbenchmarks with Nashorn.

1. Pointing out the right Nashorn jar

As of b82, nashorn is integrated into the JDK, which means that the nashorn.jar that ships with the JDK is picked unless you do one of the following, which you should do before running any nashorn benchmarks if you want to test nashorn code that you have built yourself. If you just want to benchmark the JDK nashorn.jar in your JAVA_HOME, you can omit this step

1) put the built nashorn.jar in $JAVA_HOME/jre/lib/ext, replacing the one that came with the JDK.

-wi means warmup iterations. 20 is more than enough, this gives hotspot time to optimize-i means real iterations. -f means how many JVM forks should be done, i.e. should each benchmark be started in a new JVM

Low iteration scores when stable are good. They show time per iteration in milliseconds

Modify rerun flags as needed

2.2 Using the "ant octane" job in the Nashorn source

Go to the nashorn make directory

prerequisite: run "ant externals" to download benchmarks and all other third party dependencies

Please note that 2) and 3) use the octane base.js harness, which has a very primitive and deviation prone way of measuring benchmark time. Benchmarks like splay that have very short iterations will be extremely badly affected and show widely diverging results.