[kepler-dev] [Bug 5247] Allow user to set memory allocated to Kepler from within Kepler

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5247

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cxh at eecs.berkeley.edu

--- Comment #6 from Christopher Brooks <cxh at eecs.berkeley.edu> 2012-06-20 15:53:07 PDT ---
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 at 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 at 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 at 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.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.