Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix QPS in non-optimal scenarios #227

Merged
merged 1 commit into from Dec 7, 2022

Conversation

rsevilla87
Copy link
Member

Signed-off-by: Raul Sevilla rsevilla@redhat.com

Description

The original implementation uses creates a new go-routine per replica, in scenarios where there's only one object replica per iteration (node-density), kube-burner might not reach the configured QPS ratio . This is more likely in scenarios where there're some delay from the API, like when network latency with the API is not 100% optimal.

This new implementation makes API calls not blocker since they are now encapsulated in their own go-routines.

@rsevilla87 rsevilla87 force-pushed the fix-qps branch 3 times, most recently from d0775d7 to e11bc92 Compare December 7, 2022 01:08
@rsevilla87 rsevilla87 changed the title Fix QPS Fix QPS in non-optimal scenarios Dec 7, 2022
Copy link
Contributor

@afcollins afcollins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Signed-off-by: Raul Sevilla <rsevilla@redhat.com>
@rsevilla87 rsevilla87 merged commit 1630f73 into kube-burner:master Dec 7, 2022
@rsevilla87 rsevilla87 added the bug Something isn't working label Dec 9, 2022
rsevilla87 added a commit to rsevilla87/kube-burner that referenced this pull request Nov 21, 2023
Signed-off-by: Raul Sevilla <rsevilla@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants