Skip to content

benchmark: add final clean-up to module-loader.js

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

benchmark, module

Currently, module-loader.js cleans up its temp directory only before each benchmark run. So after the last run, a tmp directory with 50,000 subdirectories and 100,000 files remains in the benchmark directory. A second final clean-up does not add much more time to overall benchmark duration because it reduces the time for each next initialization, while benchmark directory remains clean after the last run.

Merge request reports

Loading