-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Exporting worker utilization to statsD #2295
Comments
This is something we are actively searching for a solution to. Currently we scale based on CPU/Memory but that doesn't solve the problem of a pod getting several long running requests that are not CPU or memory bound. |
4 tasks
also currently I found the number of workers metric only updated when gunicorn starts. if we had a long running application, it's hard to use the metric. |
fo you mean that When *you* increase the number of workers it isn’t
updated? Otherwise the number of workers don’t increase until you send a
signal to gunicorn or update its config.
Le ven. 24 sept. 2021 à 02:51, Zhanzhao (Deo) Liang <
***@***.***> a écrit :
also currently I found the number of workers metric only updated when
gunicorn starts. if we had a long running application, it's hard to use the
metric.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2295 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADRIVYUANKLXXYPC652DTUDPDQBANCNFSM4LS5V7JA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Sent from my Mobile
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is a feature request.
Gunicorn exports some useful metrics to statsD, including the number of gunicorn workers. However, it doesn't export the number of workers currently serving a request, or equivalently, a percentage worker utilization. This is something I've been trying to figure out how to determine externally from gunicorn, and so far have been unsuccessful with. I think it might be easier to update gunicorn's statsd logging to include worker utilization, which I imagine could be found from asking the master gunicorn process how many workers are busy.
My use case for this metric is to feed it to the Kubernetes HorizontalPodAutoscaler so that I can scale my gunicorn deployment based on gunicorn worker utilization.
I would be willing to work on this and create a pull request. What do people think?
The text was updated successfully, but these errors were encountered: