feat: disable client-side throttling #3293
Merged
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.
Otherwise default to 30 QPS (60 burst QPS).
This is an increase from the rest.Config default of 5 QPS.
Based on my local performance testing, it looks like kpt v1.0.0-beta.16 has a performance regression that defaults the applier to 5 QPS. I haven't quite figured out why, but earlier versions (like v1.0.0-beta.15) are much faster.
This change both fixes the regression and removes the QPS limit on servers where server-side throttling is enabled. The beta feature flag is enabled by default on K8s v1.20+.