Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h3>Use 50% of available RAM to test:</h3> <p>You can decrease the innodb_buffer_pool_size very low to see if it helps:</p> <pre><code>#/etc/my.cnf innodb_buffer_pool_size = 1M </code></pre> <p>A rule of thumb is to set innodb_buffer_pool_size to 50% of available RAM for your low memory testing. This means you start the server and everything <em>except</em> MySQL InnoDB. See how much RAM you have. Then use 50% of that for InnoDB.</p> <p>To try many low-memory settings at once:</p> <ul> <li><a href="http://paragasu.wordpress.com/2008/12/02/very-low-memory-mysql-5-mycnf-configuration/" rel="noreferrer">http://paragasu.wordpress.com/2008/12/02/very-low-memory-mysql-5-mycnf-configuration/</a></li> </ul> <p>A more likely culprit is whatever else is on that server, such as a webserver.</p> <h3>Apache?</h3> <p>Are you using Apache and/or another webserver? If so, try to decrease its RAM usage. For example in Apache conf, consider low RAM settings like these:</p> <pre><code>StartServers 1 MinSpareServers 1 MaxSpareServers 5 MaxClients 5 </code></pre> <p>And cap the requests like this:</p> <pre><code>MaxRequestsPerChild 300 </code></pre> <p>Then restart Apache.</p> <h3>mod_wsgi:</h3> <p>If you're using Apache with mod_python, switch to Apache with mod_wsgi.</p> <h3>Pympler:</h3> <p>If it's still happening, possibly your Django is steadily growing. Try Django memory profiling with Pympler:</p> <ul> <li><a href="http://www.rkblog.rk.edu.pl/w/p/profiling-django-object-size-and-memory-usage-pympler/" rel="noreferrer">http://www.rkblog.rk.edu.pl/w/p/profiling-django-object-size-and-memory-usage-pympler/</a></li> </ul> <h3>SAR:</h3> <p>Your report of once-per-day failures, then once-per-week failures, could point to some kind of cron job running daily or weekly. For example, perhaps there's a batch process that takes up a lot of RAM, or a database dump, etc. </p> <p>To track RAM use and look for RAM spikes in the hour before MySQL dies, take a look at SAR, which is a great tool: <a href="http://www.thegeekstuff.com/2011/03/sar-examples/" rel="noreferrer">http://www.thegeekstuff.com/2011/03/sar-examples/</a></p>
    singulars
    1. This table or related slice is empty.
    1. POmysqld service stops once a day on ec2 server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjoelparkerhenderson
    1. USjoelparkerhenderson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your answer i will mark this accepted, and once i test it i will still award you extra bounty on that.
      singulars
      1. PO
      1. USAamir Adnan
    2. COSorry to say low RAM settings didn't work out even :(
      singulars
      1. PO
      1. USAamir Adnan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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