[tantalor]

Nothing to see here. Author uses Octane benchmark where bigger is better, so v8 ~26 beats the "experimental engine".

Q: What do the scores mean?

A: In a nutshell: bigger is better. Octane measures the time a test takes to complete and then assigns a score that is inversely proportional to the run time (historically, Firefox 2 produced a score of 100 on an old benchmark rig the V8 team used).

https://developers.google.com/octane/faq

[moisy]

Reproduced the lower node 0.11.10 performance on gentoo.

time node core_engine_benchmark.js

as author answered below comment, the performance gain/loss could be from switches hence the combination of latest v8/node

Clearly the blog posting focuses around the second item (as a biggest replacement reasoning) which is available on both new and old v8. I couldn't reproduce the same problem on i.e. spidermonkey cli but it's visible on node 0.10.26 / 0.11.13

[azakai]

Also, they report run times for the process - it's unclear if they are looking at the total score or the run times. If score, then it seems they are looking at it in the wrong direction, as you said. If run times, then those are meaningless in the Octane benchmark, as it estimates how many executions are possible in a fixed time frame, not how long a fixed workload takes to run.