This issue tracks adding a dedicated resource utilization benchmark tool (e.g. pubsub-cpu-benchmark under src/pubsub/benchmarks/) to measure client CPU and memory footprint across idle and active phases.
As demonstrated in PR #6050 (#6050 (comment) and https://github.com/panimidi/pubsub-demo), measuring client process CPU utilization (getrusage) when spawning thousands of publishers—both at rest and under load—is critical to prevent CPU regressions.
We should include a benchmark like this to prevent regressions in the future.
This issue tracks adding a dedicated resource utilization benchmark tool (e.g.
pubsub-cpu-benchmarkundersrc/pubsub/benchmarks/) to measure client CPU and memory footprint across idle and active phases.As demonstrated in PR #6050 (#6050 (comment) and https://github.com/panimidi/pubsub-demo), measuring client process CPU utilization (
getrusage) when spawning thousands of publishers—both at rest and under load—is critical to prevent CPU regressions.We should include a benchmark like this to prevent regressions in the future.