Bug #5247
closedAllow user to set memory allocated to Kepler from within Kepler
0%
Description
A nice feature for advanced users would be to let them set how much memory kepler is allocated (presumably a restart would be required for the change to take place).
This is in part motivated by some users who have run workflows that pass large chunks of data around as tokens, and execution has stopped with an error because of heap space errors.
Updated by Daniel Crawl about 13 years ago
This does not work when using kepler.sh.
Additionally, it appears the settings are saved in build-area/settings/memory.xml, which is not writable on shared Kepler installations; memory.xml should be written to ~/KeplerData/.
Updated by David Welker about 13 years ago
Memory.xml will currently be written in KeplerData when appropriate. (i.e. in installations, when use.keplerdata is present in /build-area)
Improvements to kepler.sh for this enhancement will occur in 2.3 or later.
Updated by jianwu jianwu almost 12 years ago
The current default max memory of Kepler is 512 MB, which is set at build-area/settings/memory.xml. It's not enough for bioKepler suite, which normally needs at least 1 GB (I usually use 2GB).
It might not be a good idea to increase current default memory size just for bioKepler. Ideally, we should be able to set different default memory size for different suites.
Updated by Derik Barseghian almost 12 years ago
(In reply to comment #4)
The current default max memory of Kepler is 512 MB, which is set at
build-area/settings/memory.xml. It's not enough for bioKepler suite, which
normally needs at least 1 GB (I usually use 2GB).It might not be a good idea to increase current default memory size just for
bioKepler. Ideally, we should be able to set different default memory size for
different suites.
This is possible, and we do so for provenance. See provenance Initialize.java. However it would be nice if there were a more general solution.
Updated by Christopher Brooks almost 12 years ago
Increasing the default memory heap size to 1 Gig.
However, I would not increase the default too much.
32-bit Windows Java implementations are limited to about 1.6 gig:
cxh@newton ~
$ java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) Client VM (build 17.0-b16, mixed mode, sharing)
cxh@newton ~
$ java -Xmx1600M -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) Client VM (build 17.0-b16, mixed mode)
cxh@newton ~
$ java -Xmx1800M -version
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
See
http://stackoverflow.com/questions/171205/java-maximum-memory-on-windows-xp
The FMI Interfaces uses a 32-bit JVM because Dymola is 32-bit because it
uses 32-bit solvers.
Updated by Ilkay Altintas over 11 years ago
Derik will increase the default memory heap size to 1 Gig.
Updated by Derik Barseghian over 11 years ago
I increased max memory to 1gb at r30353. You will have to delete your existing build-area/settings/memory.xml