Or just don't use fcgi. Django's runfcgi command uses flup package which is slow and buggy. Just switched ne of our projects to uwsgi and load average dropped from 12 to 4.
On 18 май, 21:07, Simon Connah <simon.connah...@gmail.com> wrote: > On 18 May 2011, at 10:14, Vincent den Boer wrote: > > > On Monday 16 of May 2011 14:12:45 Alexander Schepanovski wrote: > >> Do you log django's stdout/stderr. You could do that with --outlog and > >> --outerr options of runfcgi command > > > It's running with those options now. And I'm waiting for it to die again ;). > > Just as an aside you might want to look into something like daemontools which > will automatically restart services that have died. I know it is better to > fix the problem at hand but sometimes a quick fix solution like that can save > you some unnecessary downtime. > > http://cr.yp.to/daemontools/faq/create.html#why -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
