benchmark: add a benchmark for URLSearchParams creation and toString()

[debadree25]

Was trying to work on nodejs/performance#56 noticed there is no benchmark on URLSearchParams.toString() hence adding one same as benchmark/querystring/querystring-stringify.js

Refs: nodejs/performance#56

[debadree25]

I am also trying to improve the perf of URLSearchParams.toString() here f15896c, there seems to be some improvement, running this benchmark the results look something like

                                                                  confidence improvement accuracy (*)   (**)  (***)
url/url-searchparams-toString.js n=1000000 type='array'                  ***     23.29 %       ±4.91% ±6.54% ±8.51%
url/url-searchparams-toString.js n=1000000 type='encodelast'                     -4.55 %       ±4.63% ±6.16% ±8.03%
url/url-searchparams-toString.js n=1000000 type='encodemany'               *     -4.37 %       ±3.99% ±5.31% ±6.92%
url/url-searchparams-toString.js n=1000000 type='multiprimitives'                -4.40 %       ±4.43% ±5.90% ±7.68%
url/url-searchparams-toString.js n=1000000 type='noencode'                       -1.37 %       ±4.41% ±5.87% ±7.64%

Trying to follow the cues from the code of https://github.com/anonrig/fast-querystring but it seems the main bottleneck lies in the regex checking over

node/lib/internal/util.js

Line 78 in f15896c

const match = RegExpPrototypeExec(unpairedSurrogateRe, str);

which is required for spec compliance I believe? so cannot entirely copy the code from https://github.com/anonrig/fast-querystring too? If anyone has any more ideas would be grateful!!

[anonrig]

If you are only testing the performance of toString, it feels like initialization should not be inside the bench.

[debadree25]

Maybe we should spilt it into two, there is also no benchmark for the creation of the URLSearchParams object would that be good?

[debadree25]

Used all types of possible parameter types for URLSearchParams and added another benchmark for the creation of the object PTAL @anonrig

[anonrig]

cc @nodejs/performance @nodejs/url

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/50048/

[mcollina]

I think it might be more useful to compare it against querystring than on itself.

[debadree25]

Is there any example of comparative benchmarks with other functions in our benchmark tests?

[debadree25]

Ok we already have benchmark/url/legacy-vs-whatwg-url-searchparams-parse.js for comparison and this one would only add for individual perf checking @mcollina

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/50337/

[mcollina]

lgtm

[nodejs-github-bot]

Landed in 28c9fb9