waiverdb: Set fixed number of processes ans threads
New waiverdb container image starts 8 gunicorn web worker processes by default using WEB_CONCURRENCY environment variable. This causes memory to spike (over 500MiB) and workers to get terminated. Instead of increasing memory limits, a better solution is to decrease the number of processes and increase number of threads since the app mostly waits on DB requests to finish and waiverdb workers themselves are thread-safe.
This commit is contained in:
parent
cb2908cc48
commit
c6df495552
1 changed files with 5 additions and 0 deletions
|
@ -60,6 +60,11 @@ spec:
|
||||||
mountPath: /etc/fedora-messaging
|
mountPath: /etc/fedora-messaging
|
||||||
readOnly: true
|
readOnly: true
|
||||||
env:
|
env:
|
||||||
|
- name: GUNICORN_CMD_ARGS
|
||||||
|
value: >-
|
||||||
|
--workers=3
|
||||||
|
--threads=6
|
||||||
|
--timeout=90
|
||||||
- name: DATABASE_PASSWORD
|
- name: DATABASE_PASSWORD
|
||||||
valueFrom:
|
valueFrom:
|
||||||
secretKeyRef:
|
secretKeyRef:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue