X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhelp%2Fhtml%2Fmemory.html;h=0374dcba23fb31286bb95fe8dbe09ecb3ce9b169;hb=8554d8662434979c3a0bdebcc6a2cd837f2afd7c;hp=4baebf2ce41a1981beea405667ac2018e57d5c22;hpb=ee7fcf8d9d817e079c2f0498d149ec45a21f82dc;p=jalview.git
diff --git a/help/help/html/memory.html b/help/help/html/memory.html
index 4baebf2..0374dcb 100755
--- a/help/help/html/memory.html
+++ b/help/help/html/memory.html
@@ -61,8 +61,7 @@
necessary to adjust them if you are working with particularly large
datasets, or need to make room for other processes on the machine.
Jalview 2.11 includes a launcher that automatically
- configures the proportion of memory allocated to Jalview's JVM, and
- its behaviour can be altered in a number of different ways:
+ configures the proportion of memory allocated to Jalview's JVM. By default it requests up to 90% of available memory whilst ensuring that at least 0.5G is available to the operating system and at least 0.5G is available to the Java runtime platform, or a specified 'maximum memory limit' - which ever is smaller. The amount of memory requested can be altered in a number of different ways:
jalview.jvmmemmax = 32G+ Adjusting this default (via a JVL file, above) will allow larger amounts (or can limit the amount) of memory to be allocated to Jalview in conjunction with the jalview.jvmmempc setting. +
java -jar jalview-all-2.11.1.0-j1.8.jar -jvmmempc=50 -jvmmemmax=20g+ (this example will launch Jalview with a maximum heap size of the smaller of 20GB or 50% of physical memory detected). +