mitata

Mostly I want to benchmark code in our production monorepo, so a web tool doesn’t make much sense. We have a bunch of data structure code and standard utility libraries so it’s not feasible to copy everything into a web form. When doing data structure work I’ve started writing micro benchmark files with mitata (https://github.com/evanwashere/mitata) which does a decent job running GC between runs and outputs some very cute graphs and such. I recently rewrote a core container class we use at Notion and for a 5% speed up on a bunch of our public API routes. OP, I see you have a mitata-inspired benchmark library “benchmate” (https://github.com/3rd/benchmate/tree/master), I’m curious about difference from mitata, what was missing from it, features added? I looked a bit at the code and it’s certainly easier to read… mitata codebase feels like

You should write your own benchmarks! I've been using mitata for microbenchmarks which is what the bun and deno people use for their cool benchmark charts. It's fast and tries to call the system GC between runs which helps reduce bias. github: https://github.com/evanwashere/mitata I find iterating in mitata super fun and a little addictive. It's hard to write a representative micro-benchmark, but optimizing them is still useful as long as you aren't making anything worse, which is often easy to avoid. I recently used mitata-benchmark-guided optimization to rewrite a core data structure at Notion for a 5% latency decrease on a few endpoints at p90/95/99. One of our returning interns used it to assess serialization libraries and she found one 3x faster. a+++ would recommend

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...

I always had a sweet tooth for how easy it is to use google/benchmark, but when working with js, current libraries didn't feel right and some were not even accurate enough, so I decided to create my own library to make JavaScript benchmarking tooling better. With more free time, I finally implemented all features I wished for in 1.0.0 and made a lightweight C++ single-header version for moments when google/benchmark is too much. Hope this library helps you as much as it does me.