+1 to try it.
On Thu, Jun 1, 2017 at 4:15 PM, Kevin Fenzi <[email protected]> wrote: > Greetings. > > With all the work Patrick and Pingou have been doing on pagure lately, it's > much faster and it doesn't have lockups as often. Unfortunately it does still > have them. > > Currently when it does stop processing it's got 4 threads at 100% cpu doing > tasks on large git repos. I'd like to bump that to have it start 6 of them > and see if this makes the lockups happen less (ie, if the problem is that it > locks up if 4 large processes happen to hit at the same time, it should lock > up less if theres 6 processes running) > > +1s? > > kevin > -- > diff --git a/roles/pagure/frontend/templates/0_pagure.conf > b/roles/pagure/frontend/templates/0_pagure.conf > index 480b1ef..4b76d20 100644 > --- a/roles/pagure/frontend/templates/0_pagure.conf > +++ b/roles/pagure/frontend/templates/0_pagure.conf > @@ -3,7 +3,7 @@ WSGISocketPrefix run/wsgi > WSGIRestrictSignal Off > WSGIPythonOptimize 1 > WSGIPassAuthorization On > -WSGIDaemonProcess pagure user=git group=git maximum-requests=1000 > display-name=pagure processes=4 threads=4 inactivity-timeout=300 > +WSGIDaemonProcess pagure user=git group=git maximum-requests=1000 > display-name=pagure processes=6 threads=6 inactivity-timeout=300 > WSGIDaemonProcess paguredocs user=git group=git maximum-requests=1000 > display-name=paguredocs processes=4 threads=4 inactivity-timeout=300 > > ## Redirects http -> https > > > _______________________________________________ > infrastructure mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ infrastructure mailing list -- [email protected] To unsubscribe send an email to [email protected]
