-
Notifications
You must be signed in to change notification settings - Fork 743
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
Add threadiness to helm chart #643
Conversation
@mvollman changing the number of workers doesn't make any difference, Flagger has its own scheduling mechanism, each canary gets a dedicated go routine. |
We have currently increased threadiness for performance reasons in both of our k8s clusters. I set it manually before forking the helm chart. Once we got the responsiveness we wanted from the operator I tried setting |
charts/flagger/README.md
Outdated
@@ -134,6 +134,7 @@ Parameter | Description | Default | |||
`resources.limits/memory` | Pod memory limit | `512Mi` | |||
`affinity` | Node/pod affinities | None | |||
`nodeSelector` | Node labels for pod assignment | `{}` | |||
`threadiness` | Number of k8s wortkers | `2` |
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.
`threadiness` | Number of k8s wortkers | `2` | |
`threadiness` | Number of controller workers | `2` |
90e7972
to
0f1a42a
Compare
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.
LGTM
It is in fact the exact same issue. I am looking into the rate limiting now. I will collect some more data around timings. The rate limiting makes sense, but I did also see an improvement with the threadiness increase. |
Add threadiness as an option to the helm chart to increase the value beyond the default of 2 threads. Bump chart version to 1.1.0 to reflect the new chart feature.