On Tue, Jul 7, 2009 at 1:16 PM, Ramdas S <ram...@gmail.com> wrote:

> Hi,
>
> We have a web server where we are hosting around 12-15 django web sites
> most of them attracting modest traffic, except a couple which sees spiikes
> on and off. Together we estimate just about 20,000-40,000 page views.
>
> However we are expecting major spikes in traffic in the coming days and are
> moving to a 8 GB RAM quad core server.
>
> We are also trying to optimize the django apps.
>
> Presently we have memcached mod-python instances running. The database
> server is also running on the same server.
>
> What all should we do to ensure that such a server can handle huge volumes
> of traffic?


IIRC the Real World Django talk at pycon went over optimization.
http://pycon.blip.tv/file/2083844/

also, some basic info with
http://books.google.com/books?id=M9kXnUf841wC&lpg=PA471&ots=Jy8FjA5ZZy&dq=optimizing%20django&pg=PA471


>
>
> We are presently optimizing every site with whatever we can according to
> what Yahoo! recommends for improving site performance. But that's only at
> the client side.
>
> I am told that mod wsgi is more efficient than mod-python. How efficient?
> Do your recommend moving all sites to modwsgi?
>
> What about nginx? Is it worth exploring Nginx as alternative to Apache?
>
> Is there anything else we need to look at?
>
> Thanks for the advices...
>
> Also what is the realistic number of page views/ simultaneous connections
> that a Nehalem quad core Intel i-7 920, 8 GB RAM machine can handle? Any
> statistical experiences.
>
> Thanks
>
> --
> Ramdas S
>
>
>
> >
>

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

Reply via email to