Re: FBR : Greenwave gunicorn timeout back to 30s

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



After looking at the data it seems that a timeout of about 2 minutes
would improve the situation without making bodhi's cron job too long.

This is my revised patch

diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml
b/roles/openshift-apps/greenwave/templates/buildconfig.yml
index d836b482d..3ed86258f 100644
--- a/roles/openshift-apps/greenwave/templates/buildconfig.yml
+++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml
@@ -30,7 +30,7 @@ spec:

       # Become non-root again
       USER 1001
-      ENTRYPOINT docker/install-ca.sh && gunicorn-3 --workers 8
--timeout 660 --graceful-timeout 300 --bind 0.0.0.0:8080
--access-logfile=- --enable-stdio-inheritance greenwave.wsgi:app
+      ENTRYPOINT docker/install-ca.sh && gunicorn-3 --workers 8
--timeout 127 --bind 0.0.0.0:8080 --access-logfile=-
--enable-stdio-inheritance greenwave.wsgi:app
   strategy:
     type: Docker
     dockerStrategy:
-- 
2.20.1

+1s ? -1s ?

Clément

On Wed, 20 Mar 2019 at 11:57, Clement Verna <cverna@xxxxxxxxxxxxxxxxx> wrote:
>
> On Wed, 20 Mar 2019 at 11:52, Stephen John Smoogen <smooge@xxxxxxxxx> wrote:
> >
> > On Wed, 20 Mar 2019 at 05:15, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote:
> >
> > > > Sure which value would you suggests ?
> > >
> > > We have the data*, we should just look at it :)
> > >
> > > * We have stored the time it took to query greenwave for each of the 1500+
> > > updates from bodhi we've tested (83 of which have more than one build), so we
> > > should be able to look at it and see if there something in there to help us make
> > > a reasonable decision.
> > >
> >
> > If you aim me at the data I can help come up with some valid numbers..
> > and I would suggest that we look at a 80% fit. If we find a number
> > which meets 80% of queries then we are good.
>
> Thanks smooge.
>
> For the record the data location was shared on IRC.
> >
> > >
> > > Pierre
> > > _______________________________________________
> > > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> > > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> >
> >
> >
> > --
> > Stephen J Smoogen.
> > _______________________________________________
> > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux