improve documentation of the otelcol benchmarks

Component(s)

testbed

Is your feature request related to a problem? Please describe.

I’ve reviewed the OpenTelemetry Collector benchmark information at https://opentelemetry.io/docs/collector/benchmarks/ but am still unclear about several aspects of the graphs. I’m looking for a detailed explanation of each test run, along with specifics on the hardware and OS setups used for each. Also i looking for explanations and advising to tune into cpu reduction.

Describe the solution you'd like

Some of the questions I have are:

What are the CPU specifications, such as the number of cores and their types? How many cores and threads are utilized?
What does "SPS" mean in these test names? Is it “Samples per Second” or “Data per Second”?
Why does HTTP appear to have a lower CPU usage than gRPC in these benchmarks?
How is CPU usage distributed in HTTP versus gRPC tests?
Which configuration parameters are most relevant to optimize CPU usage, especially when handling lower trace volumes?
How has SPS/DPS performance evolved across different OpenTelemetry Collector versions, showing any historical trends in performance changes?
How can I trace and analyze CPU usage for my custom Collector build, especially since the benchmark seems to exclude certain widely-used receivers, processors, exporters, and extensions?
The current testbed doesn’t seem to evaluate a complete pipeline, such as an HTTP/gRPC receiver, processor, and gRPC/HTTP exporter. In that case, is HTTP truly the most efficient end-to-end option in terms of CPU usage? How would backpressure on the exporter side impact CPU and RAM usage?
How can I tune the OpenTelemetry Collector to prevent CPU spikes, similar to how memory limits can be set?

Any insights into these areas would be immensely helpful!

Describe alternatives you've considered

No response

Additional context