On May 3, 3:10 am, Robin Becker <[EMAIL PROTECTED]> wrote: > Djangophiles, is there any kind of analysis of the above combination with > regard > to efficiency. It seems that mod_fastcgi must talk to the flup server through > a > single socket (or rather each front end apache process must do so) and the > flup > server spawns flup/fastcgi children(I'm using a forking flup) to respond to > the > requests. I think there are no bottlenecks here, but I'm not sure who's > responsible for scaling up and down as requests come in. Can anybody > enlighten me?
Ultimately the network overheads in a specific hosting mechanism, although they differ between different mechanisms, are not where your bottlenecks are going to be. The real bottlenecks are going to be in your Python application code and any back end database access. So, except for avoiding CGI and not using the Django internal development server for a production system, the hosting mechanism will not matter too much. Thus, simply choose the one that you think works best for you as far as easy of installation, configuration and management. That all said, if you are still obsessive about performance, or truly are creating a site which will require super performance, you would be better off looking at mod_wsgi with Apache. For highest performance, use Apache prefork MPM with mod_wsgi embedded mode and dedicate the server to just your Python application, with static files hosted off a separate system. If running as a particular user is still important, use mod_wsgi embedded mode instead. For some comparisons of different mechanisms see: http://code.google.com/p/modwsgi/wiki/PerformanceEstimates In respect of Apache/mod_fastcgi/flup, it is generally a bit slower than mod_python, thus you can put things in context. As I said though, this is not where your bottlenecks will be. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
