https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core...
It appears that the reported numbers for benchmark X are _the # of times that X can be run before one second elapses_, so parent comment is correct and the premise of the blogpost (that the new node.js version with V8 has worse performance than the earlier version / the private fork has better performance than the new version and slightly worse performance than the old) is contradicted by the evidence presented.
Not a good way to look competent, posting something like this. Countdown until edit or takedown...
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).
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
Looking forward to it.
