From a58be5fb3401c0b0f74d6089d2eaaf7691e6418f Mon Sep 17 00:00:00 2001
From: Jim Procter
Date: Wed, 26 Feb 2020 16:58:58 +0000
Subject: [PATCH] JAL-3477 jalview.jvmmemmax / jvmmemmax maximum value
documentation
---
help/help/html/memory.html | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/help/help/html/memory.html b/help/help/html/memory.html
index 4baebf2..81190a9 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:
@@ -88,6 +87,11 @@
open /Applications/Jalview.app --args ~/mymemorysetting.jvl -open ~/myalignment.fa(put all the Jalview arguments after the --args
parameter)
+ - Maximum memory limit
+ Since 2.11.1.0, Jalview's configuration includes a 'maximum memory limit':
+ jalview.jvmmemmax = 32G
+ 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.
+
- Directly opening Jalview
with a JVM
Launching Jalview directly with a JVM is
entirely possible, but is not recommended for regular interactive
--
1.7.10.2