Repository navigation
Support per-benchmark-suite setup and teardown #58488
Description
Activity
I can take this one to work
Reacted by Pietro Marchini and Mert Can AltinHey there, I've been looking for a good first issue and if help is needed I'd also be happy to collaborate.
Reacted by Pietro Marchini and Mert Can AltinHey @symonbaikov, @NitinAtIntel,
Thank you very much for your support 🚀Any contribution is more than welcome!
Feel free to open a PR 😊
will work on this
- added a commit that references this issue
on Nov 7, 2025 - added 3 commits that reference this issue
on Nov 10, 2025 - added 3 commits that reference this issue
on Feb 17, 2026
Currently with the benchmark utility, if a benchmark needs to perform setup and tear down, it can only be done on a per-run basis. A good example would be:
node/benchmark/module/module-require.js
Line 15 in fcf5de0
This benchmark needs to create 10K files per-run, so for 60 runs * 3 configurations, it needs to create and delete 60 * 3 * 10K files, so the majority of the time spent on running the benchmark come from this process instead of the actual benchmarking that's done in between.
If for example we support setup and teardown on a per-suite basis (it doesn't necessarily have to be config-specific, a benchmark can do a setup for all the configs in one setup/teardown pair), then this would be reduced to only creating/deleting 3 * 10K files.
The setup/teardown should probably be done somewhere around here - before starting the queue and after executing the last job in the queue:
node/benchmark/common.js
Lines 234 to 241 in 7178588