4 ms·
Wait, I'm confused. From the following line: https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core_engine_benchmark.js#L228 https://github.com/Nubisa/jx
by eshyong 12y ago
Wait, I'm confused. From the following line:
https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core_engine_benchmark.js#L228 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?
- bbllee 12y ago// 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_engine_benchmark.js#L66-L75 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_engine_benchmark.js#L182-L183 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.
- moisy 12y agonumbers seem less important considering the run times.