On 12-Nov-07, at 6:25 PM, Forest Bond wrote:
> Maybe you need to decrease your ServerLimit? Each forked server > process leads > to increased memory usage. For a really low volume site, you can > get away with > ServerLimit 1, although I'd be sure to host your media files in a > different > instance (webfaction has docs for doing this somewhere). did that > > Make sure that Django and Python debug settings are disabled, too > (apache2.conf > PythonDebug, settings.py DEBUG). did all this - I am still getting around 35 MB per instance. And it is not the fault of webfaction. The same site on my local machine gives the same figure. This on the latest svn in both cases. The last time I looked at these figures, it was around 12-15mb an instance. Any other clues? -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
