Benchmark fixes #9064
Closed
Benchmark fixes #9064
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
When a benchmark did not contain any parameters the csv configuration filed would be "". In R this is by default parsed as NA, causing NA in the printout too. Fixes: #9061
This changes the execution order from "iter, file, binary" to "file, iter, binary". This means the csv no longer has to buffered completely. This also has the added effect that stopping compare.js early or interfering with performance only affects a single benchmark, instead of all of them. Refs: #8659
Using new syntax such as `...args` means that the benchmark suite can't be used with older node versions. This changes the `...args` syntax to a good old `Array.prototype.slice`. Refs: #8932 (comment)
nodejs-github-bot
added
the
benchmark
|
/cc @mscdex |
|
Not overly keen on this. But technically LGTM |
|
@jasnell Which part did you have reservations about? I can confirm the csv parsing fix works. |
|
The changes to v8ForceOptimization. It's no biggie tho. |
|
@jasnell: @trevnorris touched a bit on it in #8637 (comment).
|
|
LGTM |
jasnell
pushed a commit
that referenced
this pull request
Oct 17, 2016
When a benchmark did not contain any parameters the csv configuration filed would be "". In R this is by default parsed as NA, causing NA in the printout too. Fixes: #9061 PR-URL: #9064 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Brian White <[email protected]>
jasnell
pushed a commit
that referenced
this pull request
Oct 17, 2016
This changes the execution order from "iter, file, binary" to "file, iter, binary". This means the csv no longer has to buffered completely. This also has the added effect that stopping compare.js early or interfering with performance only affects a single benchmark, instead of all of them. Refs: #8659 PR-URL: #9064 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Brian White <[email protected]>
jasnell
pushed a commit
that referenced
this pull request
Oct 17, 2016
Using new syntax such as `...args` means that the benchmark suite can't be used with older node versions. This changes the `...args` syntax to a good old `Array.prototype.slice`. Refs: #8932 (comment) PR-URL: #9064 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Brian White <[email protected]>
jasnell
pushed a commit
that referenced
this pull request
Oct 17, 2016
When a benchmark did not contain any parameters the csv configuration filed would be "". In R this is by default parsed as NA, causing NA in the printout too. Fixes: #9061 PR-URL: #9064 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Brian White <[email protected]>
jasnell
pushed a commit
that referenced
this pull request
Oct 17, 2016
This changes the execution order from "iter, file, binary" to "file, iter, binary". This means the csv no longer has to buffered completely. This also has the added effect that stopping compare.js early or interfering with performance only affects a single benchmark, instead of all of them. Refs: #8659 PR-URL: #9064 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Brian White <[email protected]>
jasnell
pushed a commit
that referenced
this pull request
Oct 17, 2016
Using new syntax such as `...args` means that the benchmark suite can't be used with older node versions. This changes the `...args` syntax to a good old `Array.prototype.slice`. Refs: #8932 (comment) PR-URL: #9064 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Brian White <[email protected]>
|
@jasnell thanks for merging this, kinda forgot about it :) |
3 tasks
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.
Checklist
make -j8 test(UNIX), orvcbuild test nosign(Windows) passesAffected core subsystem(s)
benchmark
Description of change
Some minor benchmark fixes. I can create 3 separate pull requests if that makes the review process easier.
benchmark: fixes csv parsing given no parameters
When a benchmark did not contain any parameters the csv configuration
filed would be "". In R this is by default parsed as NA, causing NA in
the printout too.
Fixes: #9061
benchmark: change the execution order
This changes the execution order from "iter, file, binary" to "file,
iter, binary". This means the csv no longer has to buffered completely.
This also has the added effect that stopping compare.js early or
interfering with performance only affects a single benchmark, instead of
all of them.
Refs: #8659
benchmark: use node v4 syntax in common.js
Using new syntax such as
...argsmeans that the benchmark suite can'tbe used with older node versions. This changes the
...argssyntax to agood old
Array.prototype.slice.Refs: #8932 (comment)