-
Notifications
You must be signed in to change notification settings - Fork 106
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
Research/document gunicorn/gevent settings #4382
Labels
Milestone
Comments
10 tasks
I checked the PI planning document and this is slated for 13.2 |
Moving to 15.6 due to resource constraints |
Research has been done with this, however, measuring per second requests has been a blocker. We'll revisit when we have more resources in the feature. |
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like our applications can start to suffer performance issues when the database is only around 30% CPU. This could be a concurrency issue - I don't know whether this is the best approach for addressing the issue, but we should still research/document gunicorn/gevent settings. I don't know for sure how many concurrent requests we can handle for each app instance.
Helpful article: https://medium.com/building-the-system/gunicorn-3-means-of-concurrency-efbb547674b7
Docs:
With gevent:
Completion criteria
openFEC/requirements.txt
Lines 19 to 20 in ce36d69
The text was updated successfully, but these errors were encountered: