-
Notifications
You must be signed in to change notification settings - Fork 327
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
feat(*) automatically set proxy concurrency #2691
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2691 +/- ##
==========================================
+ Coverage 52.21% 52.29% +0.08%
==========================================
Files 865 865
Lines 49299 49322 +23
==========================================
+ Hits 25741 25794 +53
+ Misses 21476 21440 -36
- Partials 2082 2088 +6
Continue to review full report at Codecov.
|
This commit adds the `--concurrency` flag to kuma-dp, which is propagated to Envoy's `--concurrency` flag. On Linux, if there is no explicit concurrency, we pass `--cpuset-threads` so that Envoy will automatically scale its worker thread if it is in a cpuset. In Kubernetes clusters, we can add additional automatic controls for the Envoy concurrency. We know the amount of CPU resource reserved for the proxy container, so we can tune that automatically. If the operator knows better, then can set an explicit concurency value with a pod annotation. This fixes #1721. Signed-off-by: James Peach <james.peach@konghq.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!!
Signed-off-by: James Peach <james.peach@konghq.com>
This commit adds the `--concurrency` flag to kuma-dp, which is propagated to Envoy's `--concurrency` flag. On Linux, if there is no explicit concurrency, we pass `--cpuset-threads` so that Envoy will automatically scale its worker thread if it is in a cpuset. In Kubernetes clusters, we can add additional automatic controls for the Envoy concurrency. We know the amount of CPU resource reserved for the proxy container, so we can tune that automatically. If the operator knows better, then can set an explicit concurency value with a pod annotation. This fixes #1721. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit 1f0cf6e)
This commit adds the `--concurrency` flag to kuma-dp, which is propagated to Envoy's `--concurrency` flag. On Linux, if there is no explicit concurrency, we pass `--cpuset-threads` so that Envoy will automatically scale its worker thread if it is in a cpuset. In Kubernetes clusters, we can add additional automatic controls for the Envoy concurrency. We know the amount of CPU resource reserved for the proxy container, so we can tune that automatically. If the operator knows better, then can set an explicit concurency value with a pod annotation. This fixes #1721. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit 1f0cf6e) Co-authored-by: James Peach <james.peach@konghq.com>
This commit adds the `--concurrency` flag to kuma-dp, which is propagated to Envoy's `--concurrency` flag. On Linux, if there is no explicit concurrency, we pass `--cpuset-threads` so that Envoy will automatically scale its worker thread if it is in a cpuset. In Kubernetes clusters, we can add additional automatic controls for the Envoy concurrency. We know the amount of CPU resource reserved for the proxy container, so we can tune that automatically. If the operator knows better, then can set an explicit concurency value with a pod annotation. This fixes kumahq#1721. Signed-off-by: James Peach <james.peach@konghq.com>
This commit adds the `--concurrency` flag to kuma-dp, which is propagated to Envoy's `--concurrency` flag. On Linux, if there is no explicit concurrency, we pass `--cpuset-threads` so that Envoy will automatically scale its worker thread if it is in a cpuset. In Kubernetes clusters, we can add additional automatic controls for the Envoy concurrency. We know the amount of CPU resource reserved for the proxy container, so we can tune that automatically. If the operator knows better, then can set an explicit concurency value with a pod annotation. This fixes kumahq#1721. Signed-off-by: James Peach <james.peach@konghq.com>
Summary
This commit adds the
--concurrency
flag to kuma-dp, which is propagatedto Envoy's
--concurrency
flag. On Linux, if there is no explicitconcurrency, we pass
--cpuset-threads
so that Envoy will automaticallyscale its worker thread if it is in a cpuset.
In Kubernetes clusters, we can add additional automatic controls for the
Envoy concurrency. We know the amount of CPU resource reserved for the
proxy container, so we can tune that automatically. If the operator knows
better, then can set an explicit concurency value with a pod annotation.
I don't expect any performance changes with this PR, since in the Kubernetes
case, the proxy container already has cgroups limits enabled. I'd be happy to
run any performance regression tests if we have them though.
Full changelog
--concurrency
flag to kum-ap for setting the number of Envoy worker threadsIssues resolved
Fix #1721
Documentation
Testing
Backwards compatibility
backport-to-stable
label if the code is backwards compatible. Otherwise, list breaking changes.