You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
joyeecheung opened this issue
Nov 15, 2017
· 4 comments
Labels
benchmarkIssues and PRs related to the benchmark subsystem.buildIssues and PRs related to build files or the CI.discussIssues opened for discussions and feedbacks.
Hi all, just wondering is there anyone actually using the bench-* targets in the Makefile? This is not used by the benchmark CI, and basically those just call ./node benchmark/run.js * which is not really that hard to remember (and this does not even allow you to set the arguments at all. Besides, these days we tend to use benchmark/compare.js instead). The bench-all and bench target somehow only run a subset of the benchmarks and they are not covering all the categories that we have anyway. Based on this I think those are not maintained and not really used anymore so I am just wondering maybe we can remove those altogether.
benchmarkIssues and PRs related to the benchmark subsystem.buildIssues and PRs related to build files or the CI.discussIssues opened for discussions and feedbacks.
Hi all, just wondering is there anyone actually using the bench-* targets in the Makefile? This is not used by the benchmark CI, and basically those just call
./node benchmark/run.js *
which is not really that hard to remember (and this does not even allow you to set the arguments at all. Besides, these days we tend to usebenchmark/compare.js
instead). Thebench-all
andbench
target somehow only run a subset of the benchmarks and they are not covering all the categories that we have anyway. Based on this I think those are not maintained and not really used anymore so I am just wondering maybe we can remove those altogether.Refs: #16934
The text was updated successfully, but these errors were encountered: