News for hackers. Stuff that matters.
Re:How Node.js applications will benefit from replacing V8 i... by eshyong on Sunday May 04, 2014 @01:59PM (#7695092)
Wait, I'm confused. From the following line:

https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core...

Doesn't this line calculate the amount of time it takes to compute a single task? (elapsed time / number of runs = time per run) Doesn't this mean that JXcore is actually faster, since the number would be smaller with more runs?

Re:How Node.js applications will benefit from replacing V8 i... by bbllee on Sunday May 04, 2014 @03:50PM (#7695518)

    // Suites of benchmarks consist of a name and the set of benchmarks in
    // addition to the reference timing that the final score will be based
    // on.  This way, all scores are relative to a reference run and higher
    // scores implies better performance.

https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core...

For complete clarity, see also the lines

https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core...

The score is (arbitrary reference constant) / (geometric mean of runtime). Bad performance ==> longer runtime ==> lower scores.

Re:How Node.js applications will benefit from replacing V8 i... by moisy on Sunday May 04, 2014 @02:08PM (#7695126)
numbers seem less important considering the run times.