|
>> a case of adding -
>> -jvmmemmax=512M
Thanks for your comments, I was also going to use -jvmmemmax in the
tests. Yet, do you think it will be okay if someone with an i386 computer tries to launch Jalview (I have in mind the main Jalview application, not my tests)? Jalview will work, but I do take your point that a pre-i486 machine might struggle for interactive use. However, i386 is an architecture spec for 32-bit x86 platforms - and still pretty widespread
🙂
> Would it be reasonable to apply a default percentage for the maximum
> heap size of, say, 50 pct instead of 90? The problem is that the memory check code Jalview uses doesn't look at the shell's limits - only what's available on the machine, so the percentage calculation is not guaranteed to actually yield a size within the limits specified in
the shell. It is safer to specify a hard minimum needed for execution.
You should be able to run these tests in 128M or even 100M of working memory, but the JVM itself needs some heap .. it's a matter of finding what works I expect. We used to have default minimum of 64MB, and maximum of 256MB for all these
test operations.
Jim.
The University of Dundee is a registered Scottish Charity, No: SC015096 |