Vitest has too much memory usage in the face of a large number of benches

[D-Sketon]

Describe the bug

ref: #6535

I'm a contributor of es-toolkit. When I try to run about 200+ bench.ts using yarn vitest bench, the memory footprint is too high. I allocated 26000mb of memory for the node and it still crashes.

benchmark: https://github.com/toss/es-toolkit/tree/main/benchmarks/performance

Reproduction

• clone https://github.com/toss/es-toolkit
• install dependencies
• run vitest bench

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i5-13400F
    Memory: 20.48 GB / 31.82 GB
  Binaries:
    Node: 20.13.1 - D:\nodejs\node.EXE
    Yarn: 4.2.2 - D:\nodejs\yarn.CMD
    npm: 10.5.2 - D:\nodejs\npm.CMD
    bun: 1.1.27 - D:\nodejs\bun.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @vitest/coverage-istanbul: ^1.5.2 => 1.5.2
    vitest: ^1.5.2 => 1.5.2

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[hi-ogawa]

Since the default reporter doesn't need entire samples array, we can probably free it early and only keep track of samplesCount instead.

Reproduction by generating bench files https://stackblitz.com/edit/vitest-dev-vitest-7ovbya?file=src%2Fgen.mjs