On Oct 16, 10:21 am, Antoni Aloy <antoni.a...@gmail.com> wrote:
> 2009/10/16 Graham Dumpleton <graham.dumple...@gmail.com>:
>
> > On Oct 16, 4:59 am, Ramdas S <ram...@gmail.com> wrote:
> >> On Thu, Oct 15, 2009 at 11:11 PM, Christophe Pettus
> >> <x...@thebuild.com>wrote:
>
> >> > On Oct 15, 2009, at 10:36 AM, Ramdas S wrote:
>
> >> > > I am currently running all my sites on modwsgi apache! Though I
> >> > > cannot complain that the performance is bad, I would like to have
> >> > > more.
>
> >> > Are you certain that the web server is the performance bottleneck? In
> >> > my experience, it rarely is.
>
> >> That argument aside, can we get an answer?
>
> > But what he states is very important and shouldn't just be ignored.
>
> I agree with Grahan if you're looking for performance first you have
> to look at your own code, tune your database, then your web server and
> then perhaps you have to consider other server options.
>
> In our case our reason to move from apache+wsgi configuration to a
> ngnix + WSGI CherryPy/Tornado configuration not was performace but
> resources. Even loosing some performance the relation between the
> number of requests per second and the memory and CPU consumed in the
> computer was good enougth to justify the change.
What resources? Often this again comes down to issue of properly
setting up Apache/mod_wsgi.
If resources are limited, eg., memory, you should not for example be
using embedded mode of mod_wsgi or mod_python.
Read:
http://blog.dscpl.com.au/2009/03/load-spikes-and-excessive-memory-usage.html
If you configure things properly with Apache/mod_wsgi, there is no
reason why it should be any worse on resources than competing
solutions.
The problem is that most people just don't have a clue about how to
setup Apache well, or don't actually even investigate how Apache/
mod_wsgi can be reconfigured to address such issues. Documentation is
only useful when people read it. Mailing lists are also only useful if
you actually go asking how to do things when you don't understand.
Graham
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
