API-4 and API-16 add a new concurrent connections to stress

[joanhey]

We want to know how scale the frameworks with more users.

Some frameworks with 256 c in API-4 don't even use the 400% CPU.
But the important thing is how well they maintain more users, they scale or downgrade the performance.

Recommended, but it's for start a discussion.

API-4

• 256 c
• 1024 c

API-16

• 1024 c
• 2048 c

[MDA2AV]

This change won't improve the CPU usage, it's a framework issue if can't saturate the CPU. Was already tested with higher conn count, 256 conn doesnt mean 256 total connections, there are tens of thousands of connections done in a 256 conn 5 second test.

256 is the number of total concurrent connections at a time.

I'll test with higher value for some frameworks that cant saturate CPU, if the value doesnt change it stays 256

[joanhey]

I can test it, because we are talking about 4 Cores. And it'll show very big differences with frameworks.

PD: and never it's a framework issue with only 256 c, it's with more concurrent than we'll find frameworks issues.

[MDA2AV]

and?