> In short, if you are running Django in worker MPM for Apache, you can > be subject to sudden memory increases when you get concurrent requests > against resources which chew up a lot of transient memory. Receiving a > lot of concurrent POST requests with large content data can be one > trigger if the framework reads such POST content all into memory at > the same time. <snip> > As long as people want to run big Python web applications in memory > constrained web hosting configurations, where Apache worker MPM with a > small number of processes is the only viable solution for Apache, in > contrast to prefork MPM which isn't, this is going to continue to be > an issue. > Graham
Having recently come across Graham's comments on the Apache worker vs prefork MPM on another framework group, and being a webfaction client, I checked with webfaction which version they use. They use the prefork version, so I'd suggest Kenneth look for other possible reasons for his memory spikes in his app. My 2c on the original topic of this thread... I've been hosting with webfaction for 2 years and frequently monitor the resource usage on the shared machines hosting my sites and those of my clients (also on webfaction). Not once have any of the machines I monitor been under even moderate load, let alone heavy load - which to me speaks to their commitment to never push any of their machines to the max with user applications. Uptime has been over 99.9% for me and their support has been prompt and without fault to date. Cheers, JC --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
