[kepler-dev] Memory Useage

[Kevin Ruland]

Dan,

That would be a great savings.  It would also potentially speed up 
startup in the "populated cache" scenario.  Any changes to that system 
has to wait until we are back with a full corpus of developers (in 
particular Chad).  My opinion is some judicious use of the internal 
database would greatly simplify startup and prevent loading all the 
actors into memory simultaneously.

BTW - you can try my one line hack to ptolemy MoMLParser to see if it 
frees up enough memory to execute those workflows.  Christopher will 
probably come up with a much better solution but it appeared to work for me.

Kevin

Dan Higgins wrote:

>Hi All,
>
>    Kevin and Christopher have had several emails on memoery leaks in 
>Kepler. Even when we get the leaks fixed, I am seeing another memory 
>issue - memory useage.. I am now getting some java 'out of memeory' 
>errors on some workflows on a 512M Windows machine. I think we really 
>would like to have Kepler run on a machine with 512MB of RAM, so we 
>should do some thinking  about reducing memory use. The most obvious 
>solution I can think of is to avoid loading all actor into memory at 
>program startup.
>
>Dan
>
>  
>