feat: "deno bench" subcommand

[bartlomieju]

Closes #9175

// Defaults to 1000 warmup iterations and 1000 bench iterations
Deno.bench("URL parsing", { n: 250, warmup: 100 }, () => {
  new URL("https://deno.land");  
});


Deno.bench("URL resolving", { n: 1000 }, () => {
  new URL("./foo.js", import.meta.url);
});

$ deno bench --unstable example_bench.ts
running 2 benches from file:///Users/ib/dev/deno/example_bench.ts
bench URL parsing ... 250 iterations 23,063 ns/iter (208..356,041 ns/iter) ok (1s)
bench URL resolving ... 1000 iterations 48,045 ns/iter (250..128,625 ns/iter) ok (4s)

bench result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out (5s)

[evanwashere]

mvp

• support for up to nanoseconds accuracy and formatting
• output should also contain min/max, can be displayed as avg unit/op (min..max unit/op) or we can take inspiration from criterion.rs BenchmarkDotNet hyperfine

optional/post mvp

• warmup before measuring (10-1000 iterations or 1s worth of iterations with minimum of 4-10 iterations)
• time option to limit benchmark to time quota
• print hardware specs (see BenchmarkDotNet)
• benchmarks grouping / baseline to compare to (see hyperfine)
• compare results with previous run (see criterion)

[bartlomieju]

Note to self: ops and resource sanitizers should be ripped out from the benchmarking setup. In preliminary tests they incurred significant cost and it's not clear that they are in anyway useful for benchmarking (might kick us out of some V8 optimizations). We can reconsider them at the later stage, but they shouldn't be added in the MVP PR.

[dsherret]

LGTM!