necessary to adjust them if you are working with particularly large
datasets, or need to make room for other processes on the machine.<br />
<br />Jalview 2.11 includes a launcher that automatically
necessary to adjust them if you are working with particularly large
datasets, or need to make room for other processes on the machine.<br />
<br />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:
+ Since 2.11.1.0, Jalview's configuration includes a 'maximum memory limit':
+ <pre>jalview.jvmmemmax = 32G</pre>
+ Adjusting this default (via a JVL file, above) will allow larger amounts of memory to be allocated to Jalview in connjunction with the jalview.jvmmempc setting.