[Feature]: Stress Test is not leveraging max threads

[cijothomas]

Related Problems?

No response

Describe the solution you'd like:

https://github.com/open-telemetry/opentelemetry-rust/blob/main/stress/src/throughput.rs#L73 Shows that it only uses 1 less thread than it should be using, presumably to reserve one thread for the main loop, calculating the stats/displaying on console etc.
Given the main thread would be sleeping almost all the time, wondering if we should use all allowed threads for doing the actual work...

In short, we are not fully pushing the CPU to its max, as I only see CPU utilization around 60-70% when running this. On comparison, similar stress test from https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/test/OpenTelemetry.Tests.Stress.Metrics shows 100% CPU utilization!

Considered Alternatives

No response

Additional Context

No response

[cijothomas]

@lzchen Could you see if we can get to push the CPUs to the fullest?

[ThomsonTan]

How are cores in total in your test environment?

I only see CPU utilization around 60-70% when running this

[cijothomas]

How are cores in total in your test environment?

I only see CPU utilization around 60-70% when running this

Tried in laptop with 4 cores and in more powerful machines with 8 cores (16 logical cores). The result is same! We always use 1 less core than available!