Re: Django Web Application Cost So Many memory

Hi,

Sounds correct to me.

Regards,

Xavier.

Le 30 mars 2011 à 17:48, 付毅 a écrit :

hi Xavier Ordoquy
So , you mean 60M per python process is in a normal status? I really encouter this kind of website before

On Wed, Mar 30, 2011 at 11:35 PM, Xavier Ordoquy <xordoquy@linovia.com> wrote:

Le 30 mars 2011 à 15:41, 付毅 a écrit :

> i don't think 100 instance means to 100 CPUs. I just want to use http_load to test pressure to my web server. if i make the 100 cocurrent request per second with 100 cocurrent connection. I will make 100 python process instance when I deploy my web project in prefork environment. Any others agree with me?

If you have 100 instances, 9 of 10 which are waiting in python code, you've got a huge architecture issue.
Let a front server (nginx, apache, and co) deal with administrative tasks and let django deal with computing the pages.
There are tons of blog posts out there that explains how to do it.

Regards,
Xavier.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.