benchmark: remove problematic tls params #31816
Merged
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
jasnell
approved these changes
Feb 17, 2020
mscdex
force-pushed
the
benchmark-tls-remove-slow-param
branch
from
9a9c963 to
00f1e42
Compare
These very small values can cause crashes/exceptions to occur on some systems because most time is spent in V8 GC or in parts of node core that are not being tested (e.g. streams). PR-URL: nodejs#31816 Reviewed-By: James M Snell <[email protected]>
mscdex
force-pushed
the
benchmark-tls-remove-slow-param
branch
from
00f1e42 to
5cc0754
Compare
MylesBorins
pushed a commit
that referenced
this pull request
Mar 9, 2020
These very small values can cause crashes/exceptions to occur on some systems because most time is spent in V8 GC or in parts of node core that are not being tested (e.g. streams). PR-URL: #31816 Reviewed-By: James M Snell <[email protected]>
Merged
codebytere
pushed a commit
that referenced
this pull request
Mar 16, 2020
These very small values can cause crashes/exceptions to occur on some systems because most time is spent in V8 GC or in parts of node core that are not being tested (e.g. streams). PR-URL: #31816 Reviewed-By: James M Snell <[email protected]>
codebytere
pushed a commit
that referenced
this pull request
Mar 17, 2020
These very small values can cause crashes/exceptions to occur on some systems because most time is spent in V8 GC or in parts of node core that are not being tested (e.g. streams). PR-URL: #31816 Reviewed-By: James M Snell <[email protected]>
Merged
codebytere
pushed a commit
that referenced
this pull request
Mar 23, 2020
These very small values can cause crashes/exceptions to occur on some systems because most time is spent in V8 GC or in parts of node core that are not being tested (e.g. streams). PR-URL: #31816 Reviewed-By: James M Snell <[email protected]>
codebytere
pushed a commit
that referenced
this pull request
Mar 30, 2020
These very small values can cause crashes/exceptions to occur on some systems because most time is spent in V8 GC or in parts of node core that are not being tested (e.g. streams). PR-URL: #31816 Reviewed-By: James M Snell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These very small values can cause crashes/exceptions to occur on some systems because most time is spent in V8 GC or in parts of node core that are not being tested (e.g. streams).
Specifically, I was seeing
size=1/size=2for tls/secure-pair.js causingbench.end(0)occasionally (although it seems to have only started recently, but that could have been chance?).While looking into that I also found that similarly small
sizevalues can cause crashing due to GC-related issues for tls/throughput.js.I've also adjusted the
tlsbenchmark test to use parameters that are faster.Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes