Skip to content

test: add parallel invocation of querystring benchmark#16052

Closed
jeskew wants to merge 2 commits intonodejs:masterfrom
jeskew:test/querystring-benchmark
Closed

test: add parallel invocation of querystring benchmark#16052
jeskew wants to merge 2 commits intonodejs:masterfrom
jeskew:test/querystring-benchmark

Conversation

@jeskew
Copy link
Copy Markdown
Contributor

@jeskew jeskew commented Oct 6, 2017

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

test

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Oct 6, 2017

const runBenchmark = require('../common/benchmark');

runBenchmark('querystring', ['n=1', 'input=', 'type=']);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I believe n=1 is probably enough. Setting type= would leave some codepaths uncovered.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I've added a type and input from the regular benchmark run. This is my first time working with the node.js benchmarks; thanks for reviewing and your help.


const runBenchmark = require('../common/benchmark');

runBenchmark('querystring', ['n=1', 'input=', 'type=']);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This would result in multiple undefined values so we should at least use a existing value.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the context; I was trying to replicate the pattern used in other benchmark invocations, where an empty string is used. I've pulled in what looked like the appropriate "no-op" values from the existing benchmark.

@Trott Trott added the code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. label Oct 6, 2017
@mscdex mscdex added the benchmark Issues and PRs related to the benchmark subsystem. label Oct 6, 2017
@joyeecheung
Copy link
Copy Markdown
Member

@evanlucas
Copy link
Copy Markdown
Contributor

Thanks for the contribution!

@joyeecheung
Copy link
Copy Markdown
Member

Landed in ee587f3, thanks for your contribution and welcome to Node.js!

@joyeecheung joyeecheung closed this Oct 7, 2017
joyeecheung pushed a commit that referenced this pull request Oct 7, 2017
PR-URL: #16052
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Timothy Gu <timothygu99@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
addaleax pushed a commit to addaleax/ayo that referenced this pull request Oct 12, 2017
PR-URL: nodejs/node#16052
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Timothy Gu <timothygu99@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
targos pushed a commit that referenced this pull request Oct 18, 2017
PR-URL: #16052
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Timothy Gu <timothygu99@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

benchmark Issues and PRs related to the benchmark subsystem. code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. test Issues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants