Increase concurrency for future rounds to better showcase performance on large servers about frameworkbenchmarks HOT 2 OPEN

Increasing concurrency to 1024 after fiddling with config files shows:

• The benchmark itself becomes unstable (some verifications pass, some fail, randomly)
• Absolute numbers increase (even at low core counts!)
• Scaling curve remains very similar, peaking around 20-25 cores

Not sure if it proves or disproves anything specific but it definitely underlines that some upgrades are needed to ensure the benchmark results are believable at high core counts.

from frameworkbenchmarks.

Exist other issues like this one (#5626 is an example).

We need to remember that this bench is run with that enterprise servers, but also we run it in the cloud.
And specially we need that run locally with only one computer in local for test, before we send it the PRs to this repo.

I understand the issue, but we need to remember that this benchmark is 11 years old, and that is changing with the time. The first bench was in 2013 with i7-2600k (2º generation) with 8Gb and in the cloud with EC2.
And still all results are important in any environment, and that normally the results are relative comparable using any servers. Also not everybody will have enterprise servers in production for their applications.

I like the idea from @an-tao #5626 (comment)

Do we really need 16 and 32 concurrent users actually, even testing in local, for json, db and fortunes tests. I think that not. And the best think is that we will have faster runs, as any test need ~20 sec extra with any framework.
And I really like to see the data table information, is very informative, but the majority of people never watch it.
Still 16 and 32 concurrency give very little information actually.

1024 in place of 16 and 32 seems Ok now. But for more, it'll need a bigger toolset change. Auto calculate (checking the servers resources) or manually have 3 configs for: local, faster and enterprise.

@NateBrady23 do you think that are still relevant 16 and 32 concurrent connections ? We will have faster runs without them.

from frameworkbenchmarks.