It's worth mentioning as well that the Django "built-in" dev server is single-threaded the last time I heard, and with transferring large files / the application itself, I see a lot of your users getting "busy signals" so to speak from the server when they request pages. A few thousand pageviews a day is really too much to expect from it, especially when 30 or so people are all needing reports. As Alex mentioned, mod_wsgi requires only the .wsgi file to be touched in order to reload code. I think you're going to need Apache with several listeners to get an acceptable level of performance.
On Sat, Oct 25, 2008 at 12:27 AM, gniquil <[EMAIL PROTECTED]> wrote: > > I am deploying something for my immediate group in my company, which > has about 30 or so people. My app (report) would be viewed at most a > few thousand times day (which would already be more than most of the > current php apps out there in my group). I would like to know if it's > ok to break all the rules such as running the default server and also > use it for media (which primarily consists of some ~500k large flash > files -- I am using Flex front end). > > By the way, I really like this micro-app architecture about django, > unlike pylons. I am primarily using it for generating business reports/ > dashboards (converting large excel files to simple web apps). And this > way of loading small apps really works well. > > The reason I don't want to use apache is primarily due to 1. restarts > 2. lacking root access. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
