-
Notifications
You must be signed in to change notification settings - Fork 30k
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
benchmark: more tests to confirm benchmark code isn't broken #14951
Conversation
|
||
require('../common'); | ||
|
||
// Minimal test for domain benchmarks. This makes sure the benchmarks aren't |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That file is still a copy of the test-benchmark-domain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yikes, fixed, thanks.
const runjs = path.join(__dirname, '..', '..', 'benchmark', 'run.js'); | ||
const argv = ['--set', 'arguments=0', | ||
'--set', 'n=1', | ||
'domain']; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here also
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, thanks!
test/parallel/test-benchmark-path.js
Outdated
'--set', 'path=', | ||
'--set', 'pathext=', | ||
'--set', 'paths=', | ||
'path']; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can add:
'--set', 'props=',
to further reduce iterations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The two benchmarks that have props
each seem to have a single entry only. Are you suggesting adding props=
to future-proof things in case more entries are added later to the benchmarks? (Seems like a good idea to me. Making sure I'm not misunderstanding your suggestion.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Went and added it. Thanks.
Add minimal test to confirm that domain benchmarks run.
Add minimal test to confirm that events benchmarks run.
Add minimal test to confirm that os benchmarks run.
Add minimal test to confirm that path benchmarks run.
Add minimal test to confirm that process benchmarks run.
09b239d
to
3899126
Compare
Is it worth it to create an internal |
A case could certainly be made. I'm generally resistant to adding more functions to |
Agree -- was envisioning something similar to the way the DNS tests have a separate module for their shared logic. Is it best to open up a new PR for this change (before/after this PR is merged?) to further discuss the idea, or for the change to go along with this one? |
@maclover7 I'd say separate PR. I'm literally seconds away from landing this one. :-D (I assume this is something you want to tackle.) |
Add minimal test to confirm that domain benchmarks run. PR-URL: nodejs#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that events benchmarks run. PR-URL: nodejs#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that os benchmarks run. PR-URL: nodejs#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that path benchmarks run. PR-URL: nodejs#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that process benchmarks run. PR-URL: nodejs#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that domain benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that events benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that os benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that path benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that process benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that domain benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that events benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that os benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that path benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that process benchmarks run. PR-URL: nodejs/node#14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that domain benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that events benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that os benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that path benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that process benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that domain benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that events benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that os benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that path benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Add minimal test to confirm that process benchmarks run. PR-URL: #14951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
@Trott all of these rely on benchmark having run.js Should we backport this? |
Not worth it IMO. I'll add dont-land labels. |
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test benchmark