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
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
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, an
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
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 po
On Jan 18, 2008 8:48 AM, Peter Baumgartner <[EMAIL PROTECTED]> wrote:
> I'm serving up 6 Django apps on Ubuntu Gutsy with Ngninx 0.5.26 for a
> frontend and Apache 2.2.4 prefork MPM (tried both mod_python and mod_wsgi)
> serving Django rev. 6898. MySQL 5.045, Python 2.5.1
>
>
That's 6 projects, no
I'm serving up 6 Django apps on Ubuntu Gutsy with Ngninx 0.5.26 for a
frontend and Apache 2.2.4 prefork MPM (tried both mod_python and mod_wsgi)
serving Django rev. 6898. MySQL 5.045, Python 2.5.1
These are low traffic sites, 2 a bit more complex, 1 Satchmo install, and 3
very simple sites mostly
7 matches
Mail list logo