I've a moderatelly small apllication in production, that runs on FCGI, instead of mod-python. From stress-tests it's prooven to be very fast and responsive. FCGI is dynamically managed by Apache.
The memory footprint of my FCGI processes is around 12MB per process, In addition, my Apache processes take around 6MB each. I guess that ~18MB per process is normal in your case. A 50 MB process is quite large however, what type of processing are you doing? Also - for most of the cases you'd like to recycle an apache child after a number of requests, so set the MaxRequestsPerChild to some reasonable limit. If it is unlimited and something in your code doesn't collect garbage memory properly, or it leaks memory, you'll end up with your Apache children growing significantly, and loosing the copy-on-write pages that are shared between children. In addition, make sure you take off any Apache modules that you're not using. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
