Skip to content

benchmark: use commas in non-csv rate output

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)
  • benchmark
Description of change

This just adds commas as separators in the (non-csv) rate output to make it easier to read when dealing with larger numbers.

/cc @nodejs/benchmarking ?

Merge request reports

Loading