Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango memory usage going up with every request
    primarykey
    data
    text
    <p>I moved my first Django project from DjangoEurope to Webfaction, and that started an issue looking like a memory leak. With every single request memory usage of the server process goes up about 500kb. It never goes down. This goes on until Webfaction kills it for using too much memory.</p> <p>I can clearly see this when I refresh the Django's admin interface in my browser (although this happens with every single page, not only with admin interface - I though admin interface would be a nice test case, because there is no my code directly there). With every browser reload the memory usage goes up couple hundreds kilobytes.</p> <p>I test the memory using a command suggested by Webfaction:</p> <pre><code>ps -u publica -o rss,etime,pid,command </code></pre> <p><strong>More about my setup:</strong></p> <ul> <li>Django 1.1 (stable)</li> <li>Default Webfaction Django setup using Apache and mod_wsgi</li> <li><code>DEBUG</code> set to <code>False</code></li> <li>MySQLdb 1.2.2 from Webfaction, but after hearing it had some problems I tried version 1.2.3c. Didn't help.</li> </ul> <p><strong>Edit:</strong> I created an empty Django project - default Django configuration plus <code>django.contrib.admin</code> and fresh empty database (tried both with mysql and postgresql). I started reloading Django admin in my browser and watched memory usage. At first I saw the problem occurring - memory usage grew after every reload. But then it stabilized and stopped growing. That's consistant with how my original project behaved on Django Europe. Unfortunately on Webfaction it never seems to stabilize (or at least not within limits of memory available to my account). Any advice? </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload