[autotest] Increase WSGI process limit to 65.
We're encountering failures in the lab on some new, more heavily
loaded shards. The failures are associated with this error message:
scoreboard is full, not at MaxRequestWorkers
This increases the number of WSGI daemon processes from 40 to 65, to see
if that will alleviate the symptom.
TEST=None
BUG=chromium:708679
Change-Id: I138b1bc9b824b13ad2b084358665360300a77a89
Reviewed-on: https://chromium-review.googlesource.com/477171
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Paul Hobbs <phobbs@google.com>
diff --git a/apache/conf/django-directives b/apache/conf/django-directives
index aca3984..413efe2 100644
--- a/apache/conf/django-directives
+++ b/apache/conf/django-directives
@@ -129,7 +129,7 @@
# the autotest memory leak from biting us by setting maximum-requests,
# which will recycle each daemon process after it gets a certain number of
# web requests.
- WSGIDaemonProcess autotestapache processes=40 threads=1 maximum-requests=200
+ WSGIDaemonProcess autotestapache processes=65 threads=1 maximum-requests=200
WSGIProcessGroup autotestapache
WSGIPassAuthorization On
</IfModule>
