They run great in the CherryPy WSGI server, most at >25MB, so I don't think that is the problem.
On Jan 20, 2008 2:26 PM, Sebastjan Trepca <[EMAIL PROTECTED]> wrote: > > I think the problem lies in apps, are you super sure they don't leak? > > As a temporary solution you could set Apache to kill a process when it > consumes too much memory. > > Sebastjan > > > On 1/20/08, Matt Davies <[EMAIL PROTECTED]> wrote: > > Peter > > > > Have you tried running the websites with lighttpd FCGI instead of Apache? > > > > If you have the time and the spare resource, try it out, if your still > > having memory problems then you will eliminated apache as the problem. > > > > I doubt very much that it isn't the apache from what you've said though, and > > you might never go back :-) > > > > > > We're running alot of medium traffic sites on django, nginx lighttpd FCGI > > and we've never had any memory problems. > > > > > > > > > > > > On 18/01/2008, Peter Baumgartner <[EMAIL PROTECTED]> wrote: > > > No. > > > > > > > > > > > > On Jan 18, 2008 9:23 AM, James Bennett < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > Do you have "DEBUG = True" in your Django settings file? > > > > > > > > > > > > -- > > > > "Bureaucrat Conrad, you are technically correct -- the best kind of > > correct." > > > > > > > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
