evnwashere | 1 year ago | on: JavaScript Benchmarking Is a Mess
evnwashere's comments
evnwashere | 1 year ago | on: Show HN: Mitata – Benchmarking tooling for JavaScript
vitest is nice but it’s completely unsuited for micro-benchmarks as it ends up oom crashing after just 2 optimized out benchmarks
evnwashere | 1 year ago | on: Show HN: Mitata – Benchmarking tooling for JavaScript
i didn’t want it to be complex so it uses simple time budget + at least x amount of samples, both and more can be configured with lower level api.
in practice i haven’t found any js function that gets faster after mitata’s time budget (excluding cpu clock speed increasing because of continuous workload)
another problem is garbage collection can cause long pauses that cause big jumps for some runs, thus causing loop to continue searching for best result longer than necessary
evnwashere | 1 year ago | on: Show HN: Mitata – Benchmarking tooling for JavaScript
it was hand picked for exactly that :)
evnwashere | 1 year ago | on: Show HN: Mitata – Benchmarking tooling for JavaScript
yes, you can import mitata inside web worker and run it there, if you only need raw results you can even use lower level api https://github.com/evanwashere/mitata?tab=readme-ov-file#giv...
evnwashere | 1 year ago | on: Show HN: Mitata – Benchmarking tooling for JavaScript
I have been thinking of reusing/creating something like https://perf.rust-lang.org/ that lets you pick and compare specific hash/commit with all data from json format
evnwashere | 1 year ago | on: Show HN: Mitata – Benchmarking tooling for JavaScript
It works anywhere where javascript works, so you can easily run it in browser too. Tho idea of making jsbench like website but with mitata accuracy (+ dedicated runners) keeps bugging me.
page 1
it provides bunch of features to help avoiding jit optimization foot-guns during benchmarking and dips into more advanced stuff like hardware cpu counters to see what’s the end result of jit on cpu