Add SLI Read-Only Test Scenario 10 Nodes with 1000 Pods #183
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wonderyl
reviewed
Jul 4, 2025
contrib/internal/manifests/loadprofile/read_only_node10_job1_pod1k.yaml
Outdated
Show resolved
Hide resolved
wonderyl
reviewed
Jul 4, 2025
contrib/internal/manifests/loadprofile/read_only_node10_job1_pod1k.yaml
Outdated
Show resolved
Hide resolved
wonderyl
reviewed
Jul 4, 2025
wonderyl
reviewed
Jul 4, 2025
contrib/internal/manifests/loadprofile/read_only_node10_job1_pod1k.yaml
Outdated
Show resolved
Hide resolved
wonderyl
reviewed
Jul 4, 2025
contrib/internal/manifests/loadprofile/read_only_node10_job1_pod1k.yaml
Outdated
Show resolved
Hide resolved
wonderyl
reviewed
Jul 7, 2025
wonderyl
reviewed
Jul 10, 2025
wonderyl
reviewed
Jul 10, 2025
wonderyl
reviewed
Jul 10, 2025
wonderyl
reviewed
Jul 10, 2025
wonderyl
approved these changes
Jul 11, 2025
fuweid
approved these changes
Jul 15, 2025
| []cli.Flag{ | ||
| cli.IntFlag{ | ||
| Name: "total", | ||
| Usage: "Total requests per runner (There are 10 runners totally and runner's rate is 1)", |
There was a problem hiding this comment.
Suggested change
| Usage: "Total requests per runner (There are 10 runners totally and runner's rate is 1)", | |
| Usage: "Total requests per runner (There are 10 runners totally and runner's rate is 10)", |
fuweid
pushed a commit
that referenced
this pull request
Jul 17, 2025
Addresses: [Review comment on PR #183](#183 (review)) Adjust runner rate from 1 to 10 according to load profile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds an SLI (Service Level Indicator) test scenario to
kperffor measuring the latency of read-only Kubernetes API calls, following the guidelines outlined in the [Kubernetes API call latency SLOs](https://github.com/kubernetes/community/blob/master/sig-scalability/slos/api_call_latency.md).Test Scenario
This scenario measures the latency of read-only operations on Pod resources:
staleList: Lists Pod resources without requiring quorum-level freshness.staleGet: Retrieves a specific Pod resource using stale (non-quorum) data.These request types are selected to evaluate the responsiveness of the API server under read load conditions.
#TODO: more resources (jobs, nodes, configmaps) to be added in next PR
