Use <b>free -m</b> for a quick look at your memory usage<br><br>output <br> total used free shared buffers cached<br>Mem: 3953 1698 2254 0 90 785<br>
-/+ buffers/cache: 822 3131<br>Swap: 6015 0 6015<br><br>use<b> vmstat -s</b> to see if your swapping <br>vmstat<br><br>output <br><br> 4048108 K total memory<br> 1747880 K used memory<br>
866392 K active memory<br> 560416 K inactive memory<br> 2300228 K free memory<br> 93160 K buffer memory<br> 804660 K swap cache<br> 6160380 K total swap<br> 0 K used swap<br>
6160380 K free swap<br> 96978 non-nice user cpu ticks<br> 541 nice user cpu ticks<br> 44279 system cpu ticks<br> 10538685 idle cpu ticks<br> 25511 IO-wait cpu ticks<br> 6 IRQ cpu ticks<br>
962 softirq cpu ticks<br> 0 stolen cpu ticks<br> 693226 pages paged in<br> 826457 pages paged out<br> <b> 0 pages swapped in #<span style="color: rgb(204, 0, 0);">not swapping</span><br>
0 pages swapped out</b> #<span style="color: rgb(204, 0, 0);"> not swapping</span><br> 6823749 interrupts<br> 24520953 CPU context switches<br> 1299596129 boot time<br> 4074 forks<br><br>Java processes can be passed a -Xmx option. This controls the maximum Java memory
heap size. It is important to set a limit on the heap size, otherwise the heap will
keep increasing until you get out of memory errors.<br>If you are running a custom Java application, check there is
a -XmxNNm (where NN is a number of megabytes) option on the Java command line.<br><br><br>Bash Java command<br>java -Xmx1G -Xms1G -jar your_server.jar That would allocate one gig of ram for Java. (way too much)<br><br>
I am not a Java master but I hope that helps, Ron<br>