Local benchmark.sh fail

[joanhey]

In local need to use the max number of locals CPUs.

==============================================
=== workerman / baseline / 512c (p=1, r=0, cpu=64) ===
==============================================
docker: Error response from daemon: range of CPUs is from 0.01 to 8.00, as there are only 8 CPUs available

[BennyFranciscus]

The benchmark profiles hardcode cpu=64 which maps to Docker's --cpus flag. On a local machine with fewer cores, Docker can't allocate more than what's available.

Quick workaround: you can override the cpu count in the profile or pass it directly. Something like:

# Check your available CPUs
nproc

# Then either edit the profile or run with a lower cpu value

Though ideally the script could cap cpu to $(nproc) automatically when running locally. @MDA2AV would a --local flag or auto-detection make sense here?

[MDA2AV]

@BennyFranciscus Ok for this test it need to automatically detect if the machine number of cores cant support 64 and dynamically adjust

[BennyFranciscus]

Makes sense. Something like capping cpu to $(nproc) early in benchmark.sh should do the trick — if the profile asks for 64 but the machine only has 8, just clamp it down and log a warning so people know the results aren't directly comparable to the CI runs.

Want me to put together a PR for that?

[MDA2AV]

@BennyFranciscus sure

[joanhey]

Also in local ask for change [tune] Setting CPU governor to performance...

And for that ask the password.
I don't know if can be optional and don't ask the password.

[BennyFranciscus]

Good point @joanhey — the CPU governor tuning uses cpupower which needs root, so it hits you with a sudo prompt. For local runs that's pretty annoying.

I think the move is to make tuning best-effort: try to set the governor, and if it fails (no sudo, no cpupower installed, etc.), just log a warning and keep going. The results won't be as stable without pinned frequency, but for local testing that's totally fine.

I'll bundle that into the same PR with the CPU count clamping @MDA2AV approved above — both are "make local runs not explode" fixes.

[BennyFranciscus]

PR up: #246

Caps --cpus to $(nproc) when the profile asks for more than the machine has, and makes all the sudo-requiring tuning (governor, sysctl, Docker restart) best-effort with warnings — so no more password prompts blocking the run on local machines.