4 ms·
I'm concerned about these 'benchmarks'. They are using nanosecond timing intervals. By design, CPU clocks have jitter to resist timing attacks. Secondly, a s
by rcgorton 6y ago
I'm concerned about these 'benchmarks'. They are using nanosecond timing intervals. By design, CPU clocks have jitter to resist timing attacks. Secondly, a single clock tick is much more than a nanosecond.
I would feel much more comfortable with performance comparisons (in ANY language) when the duration is on the order of minutes.
- aphyr 6y agoCriterium (the benchmarking library used here) uses multiple runs to obtain tighter bounds on amortized performance, as well as techniques to account for the effects of garbage collection and JIT compilation. See https://github.com/hugoduncan/criterium https://github.com/hugoduncan/criterium for a brief overview, as well as links to the pitfalls and statistical techniques involved in JVM benchmarking.
- nahuel0x 6y ago> By design, CPU clocks have jitter to resist timing attacks. Where did you get that info? Never saw anything like that.