Is it by accident that "mitata", the project name, means "to measure" in Finnish?
Show HN: Mitata – Benchmarking tooling for JavaScript
11–20 of 27 posts
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#12Is it by accident that "mitata", the project name, means "to measure" in Finnish?
it was hand picked for exactly that :)
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#13This is for "headless" JavaScript outside the browser, right?
Never heard JS called "headless". Not sure I like it.
edit: all JS is "headless". almost all languages are headless. _Software_ can be headless or have a GUI. but languages are naturally headless.
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#14This is for "headless" JavaScript outside the browser, right?
Never heard JS called "headless". Not sure I like it. edit: all JS is "headless". almost all languages are headless. _Software_ can be headless or have a GUI. but languages are naturally headless.
Headless browsers. I guess this is a very closely related concept.
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#15Wow, I was just looking how to benchmark a streaming JSON parser that I'm working on! I'm creating it specifically for performance-intensive situations with JSON strings sizes up to gigabytes, and I thought that I had to implement about half of the features you mention there, like parametrisation and automatic GC after every test.
When you say streaming JSON parser, do you mean that it outputs a live “observable” object as it is steaming, or that it just doesn’t keep the entire source data in memory? I’ve done some work for the former for displaying rich LLM outputs as they are delivered - it’s a surprisingly underexplored area from what I’ve seen.
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#16Hi! In your benchmark, do you use a fixed number of iterations to stop the test, or do you apply a statistical criterion, such as the Student's t-test, to determine when to stop?
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#17This is for "headless" JavaScript outside the browser, right?
Never heard JS called "headless". Not sure I like it. edit: all JS is "headless". almost all languages are headless. _Software_ can be headless or have a GUI. but languages are naturally headless.
There’s a lot of server side js. Mostly plumbing code but there’s certainly “headless” js
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#18This is awesome! I’ve been working on optimizing a javascript library recently and am feeling the pain of performance testing. I’ll check this out.
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#19Hi! In your benchmark, do you use a fixed number of iterations to stop the test, or do you apply a statistical criterion, such as the Student's t-test, to determine when to stop?
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
Re: Show HN: Mitata – Benchmarking tooling for JavaScript
#20Earlier quoted context omitted.
Never heard JS called "headless". Not sure I like it. edit: all JS is "headless". almost all languages are headless. _Software_ can be headless or have a GUI. but languages are naturally headless.
There’s a lot of server side js. Mostly plumbing code but there’s certainly “headless” js
I'm very aware of JS run on servers. And I knew that's what OP meant. I'm saying I'm not sure I like the usage. Maybe it's a generational dev vocabulary thing... I prefer "browser" or "client" JS vs "server" or backend