5 ms·
Definitely going to try this out!! I’ve been using the `vitest bench` command; being able to slap a `.bench.ts` file next to a module and go to town is conveni
by FractalHQ 2y ago
Definitely going to try this out!!
I’ve been using the `vitest bench` command; being able to slap a `.bench.ts` file next to a module and go to town is convenient: https://vitest.dev/guide/features.html#benchmarking https://vitest.dev/guide/features.html#benchmarking
- evnwashere 2y agovitest is nice but it’s completely unsuited for micro-benchmarks as it ends up oom crashing after just 2 optimized out benchmarks
- utkut 2y agoYeah, I’ve hit those OOM issues with vitest before too. Mitata’s time budget + sample approach sounds like a solid way to keep things simple while avoiding those long GC pauses. Excited to give it a try on my own benchmarks!
- zoubingwu 2y agoThat's very interesting. I saw some screenshots of benchmarks used by Bun and Deno on Twitter at that time and it inspired me to suggest to Vitest to add a benchmark command. Later I learned that they were all using Mitata internally. https://github.com/vitest-dev/vitest/issues/917#issuecomment-1126743240 https://github.com/vitest-dev/vitest/issues/917#issuecomment... Very good work and design, glad to see a stable 1.0 is released!