Reduce the numbers of iterations in benchmarkshttp/check_is_http_token

[mcollina]

• Version: master
• Platform:
• Subsystem: benchmarks

Currently benchmark/http/check_is_http_token takes several hours to complete if we try to compare two different Node versions. I think we should lower the number of iterations to simplify benchmarking the whole of http.

Specifically, I propose to revert this commit 39fdf07, or to reduce the number to something in between.
This was part of #6570.

@mscdex @nodejs/benchmarking what do you think?

[mscdex]

To be honest, what the benchmarks in general could use is either some way to have specific n values for different mixes of inputs (would require some extra logic in each benchmark file) or we just switch to some sort of time-based mechanism for these synchronous benchmarks (would require some coordination with the benchmark runner).

[bnoordhuis]

@mcollina Ping. Do you want to follow up?

[mcollina]

I'm open to discuss this, but I do not see any actionable comment so far. What do we want to do?

[BridgeAR]

This changed recently again in #14002. Closing this therefore.