benchmark: fix EADDRNOTAVAIL error in http2

[rickyes]

Fixes: #34061

It is found that there may be errors caused by too many TCP connections. This PR is only to reduce the number of connections to avoid benchmark tests crashing. On my macOS, when the value of duration is 2, there will be no errors basically.

/cc @addaleax @BridgeAR @jasnell

Checklist

• tests and/or benchmarks are included
• commit message follows commit guidelines

[joyeecheung]

Not sure whether it's a good idea to lower the default value, but you can just pass --set duration=2 to the benchmark script by the way.

[mcollina]

lgtm

[mcollina]

I think you can also change the ulimit of your system.

[mcollina]

On second thought I don't think this is needed.

[rickyes]

Refs: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/660/console

@mcollina But then we wouldn't be able to run the http2 benchmarks on jenkins unless we allow duration to be configured on jenkins.

[rickyes]

Or any good suggestions ?

[github-actions]

This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open.

[github-actions]

Closing this because it has stalled. Feel free to reopen if this PR is still relevant, or to ping the collaborator who labelled it stalled if you have any questions.