Skip to content

Conversation

@ronag
Copy link
Member

Currently we only consider write when benchmarking.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Currently we only consider write when benchmarking.
@nodejs-github-botnodejs-github-bot added benchmark Issues and PRs related to the benchmark subsystem. stream Issues and PRs related to the stream subsystem. labels Dec 23, 2019
@ronagronag changed the title benchmark: include writev in benchmarkbenchmark: include writev & callback in benchmarkDec 23, 2019
@ronagronag mentioned this pull request Dec 23, 2019
4 tasks
Copy link
Member

@BridgeARBridgeAR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This actually requires the following test to be changed:

test/benchmark/test-benchmark-streams.js

@ronag
Copy link
MemberAuthor

This actually requires the following test to be changed:

test/benchmark/test-benchmark-streams.js

Sorry, this is new for me. What is that and how does it need to be changed?

@BridgeAR
Copy link
Member

If you run the test with this addition, it will fail due to the added options that are not included in the test. It is a way to verify that at least one benchmark option passes for all benchmark files of the specific subsystem.

You could add something like writev: 'yes', callback: 'no'.

@ronagronag requested a review from BridgeARDecember 25, 2019 10:27
@BridgeARBridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Dec 25, 2019
@BridgeAR
Copy link
Member

Lite-CI https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/4115/

Marking as author ready. The benchmark test should be run while landing to verify that it works properly.

@BridgeAR
Copy link
Member

BridgeAR commented Dec 25, 2019

Landed in f68285b 🎉

BridgeAR pushed a commit that referenced this pull request Dec 25, 2019
Currently we only consider write when benchmarking. PR-URL: #31066 Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
BridgeAR pushed a commit that referenced this pull request Jan 3, 2020
Currently we only consider write when benchmarking. PR-URL: #31066 Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
@BridgeARBridgeAR mentioned this pull request Jan 7, 2020
targos pushed a commit that referenced this pull request Jan 14, 2020
Currently we only consider write when benchmarking. PR-URL: #31066 Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
@targostargos mentioned this pull request Jan 15, 2020
BethGriggs pushed a commit that referenced this pull request Feb 6, 2020
Currently we only consider write when benchmarking. PR-URL: #31066 Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
@MylesBorinsMylesBorins mentioned this pull request Feb 8, 2020
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.benchmarkIssues and PRs related to the benchmark subsystem.streamIssues and PRs related to the stream subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@ronag@BridgeAR@addaleax@lundibundi@nodejs-github-bot