[kepler-users] Kepler Memory Usage

[Matt Jones]

Yes -- you can set the max heap size by giving "-Xmx4096m" as an argument to
the java command that you use to start kepler.  Set whatever  maximum heap
size you need, but also note that this may limit some memory-intensive
actors from working properly.  I presume that you are using a shell script
to start Kepler, so its a simple addition to that script.

Note that we have found some memory leaks with the released version of
Kepler, and that those are being fixed over the next couple of releases.  I
believe that some of the most pressing memory issues will be fixed in the
upcoming release, and that others will be folded in over time. Others on
this list may be able to provide more details about these issues and the
timeline for memory fixes.

Matt

On Thu, Mar 17, 2011 at 11:14 AM, Liu, Qing <liuq at ornl.gov> wrote:

> Hi,
>
> I am currently using Kepler 2.0 and it looks like my Kepler got killed when
> I tried to launch it on a cluster machine. The system policy limits one
> process to 4GB memory and Kepler consumed 8 GB. Is there any way that we can
> reduce the Kepler memory consumption? Thanks!
>
> Gary
>
>
>
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/attachments/20110317/b2c26ac4/attachment.html>