Let me add, that this could simply be SQL overloaded right now. We had managed to get all the servers down to 2-4 load, sometimes a little more. Problem was something related to python creating zombie processes, and the other guy I worked with managed to find a solution.
We may test postgreSQL to see if this fixes our latest problem, as our SQL cluster isnt setup yet as the hoster didnt have it ready, and this is a peak traffic day. Also that multithreading weakref fix, that may help a lot :) That was the exact error we were getting when using threaded mode and it was completely random. I'll implement that and hopefully it will make it so we can drop prefork. On Dec 6, 1:40 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > We tried Apache and it seemed slower. We're doing probably 1-2 million > uniques today and the sessions are now killing the website :) > > This is on like 12 web servers now too. > > On Dec 4, 11:42 am, Fredrik Lundh <[EMAIL PROTECTED]> wrote: > > > [EMAIL PROTECTED] wrote: > > > We are running lighttpd with fastcgi in prefork mode. We tried using > > > threaded but django spits out an error about a weakly-referenced > > > object, related to sessions I believe, no longer existing.it's not > > > related to this, by any chance: > > >http://wolfram.kriesing.de/blog/index.php/2006/multithreading-with-my... > > > </F> --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
