On Fri, Mar 17, 2017 at 09:41:02AM -0600, Tim Flink wrote:
Production resultsdb is still really slow and we're still seeing
the
occasional error on result posting so I'd like to bump the resources
allocated to the wsgi app again.
I wonder if this doesn't saturate the server at one point
I'm +1 to apply because it's easy to revert but I'm not sure it's the
right
solution
Pierre
From 3d45155959cbdcde39c1a98a584a100b590761db Mon Sep 17 00:00:00
2001
From: Tim Flink <tflink(a)fedoraproject.org>
Date: Fri, 17 Mar 2017 15:33:49 +0000
Subject: [PATCH] bumping resultsdb wsgi resources again
---
roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2
b/roles/taskotron/resultsdb-ba index 97e73b9..c3f4d5c 100644 ---
a/roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 +++
b/roles/taskotron/resultsdb-backend/templates/resultsdb.conf.j2 @@ -1,5
+1,5 @@ {% if deployment_type in ['stg', 'prod'] %}
-WSGIDaemonProcess resultsdb user=apache group=apache threads=100
processes=5 +WSGIDaemonProcess resultsdb user=apache group=apache
threads=200 processes=20 {% else %}
WSGIDaemonProcess resultsdb user=apache group=apache threads=5
{% endif %}
--
1.8.3.1