bechmark: scale up RPS to test data plane CPU performance #7810
+112
−49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
This PR adjusts the Envoy Gateway benchmark to measure data plane CPU performance using RPS instead of route count.
While route count is useful for evaluating the CPU performance patterns of the control plane(EG) , data plane(Envoy) CPU usage is primarily driven by request processing. Scaling load by RPS provides a more stable signal, and makes the results easier to interpret for data plane performance analysis.
It also fixes a bug in the current sampling logic where the sample data is set to 0 when failed to query Prometheus, now the failed sampling data is not considered when calculating the min/max/men in the report.
The current bechmark report:
