While working with a 114,996 point Statistics:-ScatterPlot in xmaple I keep running out of memory.  I am receving the following output to the terminal I used to start xmaple although no errors are reported via the GUI.  Once these errors start appearing in the terminal my plot (in its own window) still responds but it becomes unusably slow.

Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap space

I don't know what the issue is with the Garbage Collector (GC).  Perhaps it is just an artifact of the Java heap space being full.  Looking at my Maple memory usage it looks like java, mserver and mjava all together are using just over 1GB of resident memory.

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
12962 don       20   0  972m 681m  29m S    0 17.2   6:21.41 java               
12992 don       20   0  423m 363m 4536 S    0  9.2   0:33.21 mserver            
13006 don       20   0 1360m  61m  19m S    0  1.5   0:18.94 mjava              

I am working on a 64-bit Linux system with 4GB of physical memory so it seems that Maple could be making use of more of the available memory before I should expect to see out  of memory errors.  The status bar in the Mape document reports 169.34M which does not appear to correlate with any of these processes.

Is there a configuration parameter I could be using to encourage Maple to make use of all available system memory?