-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test the benchmarks at one iteration #12068
Comments
Ah, only for e.g. some still run iterations even when it is set to |
Refs: #12025 |
Refactor benchmark/_http-benchmarkers.js and add a test double HTTP benchmarker for testing. PR-URL: nodejs#12121 Refs: nodejs#12068
PR-URL: nodejs#12121 Refs: nodejs#12068
@Fishrock123 were you interested in the results, or do you just want to make sure the benchmark suite doesn't regress? Because AFAIK #12326 & #12121 currently only give green/red... |
@refack I think the OP means we need to make sure that we can run the benchmarks on the platforms we support without throwing errors? Like to make sure the suite won't be broken by a PR without a CI run. |
I want to make sure the benchmarks even run. |
Cool. |
@targos I'd say not quite yet, although I'm getting there. Between what's currently in the code base and what I now have PRs open for, there are 16 tests done and 15 more to go. Here are the 15 that remain:
I'd been planning on doing all of these, but if someone wants to pick some off before I get around to it, awesome. (Maybe just drop a note here so I don't bother with whatever you're working on. Also, might be good to wait for #15004 to land. Should greatly simplify things.) |
@nodejs/testing @nodejs/benchmarking ... ping... would be great to get this one completed. |
This is done now. Closing. |
Of course we don't want to "actually" run the benchmarks during a test run. However, the benchmark runner already is able to set how many iterations the benchmarks run, and we could probably extend that even more.
As such, I don't see much reason to not run most of the benchmarks during a normal test run, with e.g. only one iteration set.
Or, at the very least perhaps we could have some sort of special CI job that does that, to be run, say, weekly.
cc @nodejs/testing @nodejs/benchmarking
The text was updated successfully, but these errors were encountered: