-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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: add benchmark for dns.promises.lookup() #27249
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
benchmark
Issues and PRs related to the benchmark subsystem.
dns
Issues and PRs related to the dns subsystem.
labels
Apr 16, 2019
richardlau
approved these changes
Apr 16, 2019
2 tasks
Trott
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Apr 16, 2019
mihalskiy
approved these changes
Apr 16, 2019
addaleax
approved these changes
Apr 16, 2019
benchmark/dns/lookup-promises.js
Outdated
return; | ||
} | ||
await lookup(name, opts); | ||
cb(); |
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.
If we’re using async/await anyway, would using a loop instead of recursive function calls make sense?
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.
Done. PTAL
Trott
force-pushed
the
add-dns-lookup-promises-benchmark
branch
from
April 18, 2019 05:21
82af24d
to
449eee0
Compare
Adding this benchmark will let us check the performance implications of nodejs#27081.
Trott
force-pushed
the
add-dns-lookup-promises-benchmark
branch
from
April 18, 2019 05:24
449eee0
to
57a9ad9
Compare
ZYSzys
approved these changes
Apr 18, 2019
Landed in f98679f |
Trott
added a commit
to Trott/io.js
that referenced
this pull request
Apr 18, 2019
Adding this benchmark will let us check the performance implications of nodejs#27081. PR-URL: nodejs#27249 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
This was referenced Apr 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
benchmark
Issues and PRs related to the benchmark subsystem.
dns
Issues and PRs related to the dns subsystem.
promises
Issues and PRs related to ECMAScript promises.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding this benchmark will let us check the performance implications of
#27081.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes