[kepler-dev] [Bug 3106] - Out of memory while opening all demos, is -Xss5m or SVG the problem?
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Tue Jan 29 16:59:09 PST 2008
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3106
cxh at eecs.berkeley.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P4
Target Milestone|1.0.0rc1 |Post-rel-1.0.0
------- Comment #2 from cxh at eecs.berkeley.edu 2008-01-29 16:59 -------
I did an experiment under Windows with Java 1.5.0_14 where I changed
-Xmx and -Xss and then used the about: facility to display all the ptolemy
demos.
Below is the output
-Xmx -Xss Windows Mem Windows Peak Mem # of Windows before
running out of memory
512m 5m 362M 365M 36
512m 10m 352M 380M 22
512m 3m 551M 551M 56
1024m 3m 387M 387M 45
1024m 2m 524M 527M 53
1024m 1m 811M 811M 80 (test completed)
1024m not set 807M 808M 80 (test completed)
Note that not all the memory is getting used when we specify -Xss of 2m or
greater.
Note also that there is some sort of non-linear relationship between
-Xmx and -Xss. We get more windows with -Xmx512m -Xss3m than we do
with -Xmx1024m and -Xss3m.
What I think is happening is that this test opens a bunch of models
quickly. -Xss sets the stack size per thread. Each of the models is
probably invoking a number of threads to get images etc.
Thus we are running out of memory.
It could be that this test is somewhat artificial, so I'm downgrading this
bug in priority and moving the milestone.
If people complain about running out of memory, and they are not using
the ENM actors, then they can change -Xss. I think setting -Xss to 5m
might be a little high, but let's wait and see if there are complaints
before changing it.
More information about the Kepler-dev
mailing list