On 25-Nov-07, at 3:49 AM, David Sissitka wrote:
>> I used to be very prowebfaction- they have huge memory leak >> problems and unless you stop and start apache once every 20 minutes, >> you very easily go over the memory limits. I now feel they are only >> good for toy sites. > > There are no known memory leaks in our Django stack, if you think > you've found one submit a support ticket and we'll be glad to look > into it. Every once in a while someone thinks they've found a memory > leak in our Django stack but nine tines out of ten the problem is that > they've DEBUG set to True in their settings.py. then why do you recommend that apache be restarted on 17,37 and 57 minutes? In fact *you* yourself install that cronjob on all django sites.? debug is false everywhere, apache is tweaked as per your recommendations and static media is served through the system wide apache. My client had to upgrade to 80 MB from 40 MB for a site that is 90% admin and has at the most, three users at a time. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ Foss Conference for the common man: http://registration.fossconf.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 -~----------~----~----~----~------~----~------~--~---
