Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm guessing you're running into 'swapping'.</p> <p>As you'll know Linux swaps out some memory to disk. This is great for memory that's not accessed very much.</p> <p>When Java starts eating heaps and heaps, linux starts:</p> <ol> <li>Swapping memory block A out to disk to make space to read in block B</li> <li>Reading/writing block B</li> <li>Swapping block B to disk to make space for some other block.</li> </ol> <p>As disk is 1000s of times slower than RAM, as the memory usage increases your machine grinds more and more closer to a halt.</p> <p>With 256 MB Cloud Servers you get 512 MB of Swap space.</p> <hr> <p><strong>Checking:</strong></p> <p>You can check if this is the case with <code>free -m</code> .. <a href="http://www.linuxatemyram.com/" rel="nofollow">this page</a> shows how to read the output: </p> <p>Next I'd check with 'iostat 5' to see what the disk IO rate on the swap partition is. I would say a write rate of 300 or more means you're almost dead in the water. I'd say you'd want to keep the write rate of the swap partition down below 50 blocks a second and the read rate down below 500 blocks a second .. if possible both should be zero most of the time. Remember disk is 1000s of times slower than RAM.</p> <p>You can check if it's Java eating the ram by running <code>top</code> and hitting <code>shift+m</code> to order the processes by memory consumption.</p> <p>If you want .. you can disable the swap partition with <code>swapoff -a</code> .. then open up the web console, and hit the site a bit .. you'll soon see error messages in the console like 'OOM Killed process xxx' (OOM is for Out of Memory I think). If you see those that's linux trying to satisfy memory requests by killing processes. Once that happens, it's best to hard reboot.</p> <hr> <p><strong>Fixing:</strong></p> <p>If it's Java using the RAM .. <a href="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rprf_javamemory.html" rel="nofollow">this link</a> might help.</p> <p>I think the easy fix would be just to upgrade the size of the Cloud Server.</p> <p>You may find a different Java RTE may be better.</p> <p>If you run it in <a href="http://ubuntuforums.org/showthread.php?t=24575" rel="nofollow">a 32 bit chroot</a> it may use less RAM.</p>
    singulars
    1. This table or related slice is empty.
    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.
    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