On 20/03/07, Nuno Mariz <[EMAIL PROTECTED]> wrote:
>
> The processing is nothing in special, right now a weblog and a online
> store.
> I've removed some modules, like fcgi, include and suexec(I can't
> remember the instalation of this modules ;) ) and the size of the
> processes is now 22Mb.
> Do you have KeepAlive On?
> In my case did't solve the problem.
> Also, can I reduce the memory footprint if I had a independent server
> to serve static media, like lighttpd?

If you have a lot of static content, you definitely want to have a
separate server to handle that. Even if it is Apache - just use a
stripped down version (no funky modules) to serve your static data,
and keep the django system separate. All of the Django tutorials
recommend using a separate server for static files - extensively.

Try locating any other modules you're not using and turning them off.
For most of the performance tests I've done on systems running
mod-python/mod-perl, it really makes a difference - sometimes
immediately noticeable.

I've keep alive off, for many cases in serving dynamic content
KeepAlive in Apache will not help you at all. When it comes to serving
static content, and especially lots of javascript/css/image files for
web-pages, then it's a blessing - you can keep it on on your static
file server, whether it's Apache or something smaller/faster.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to