Re: Garbage collection and Memory [message #2303 is a reply to message #2174] |
Thu, 09 June 1994 15:00   |
eharold
Messages: 12 Registered: July 1993
|
Junior Member |
|
|
In article <thompson.770745164@serts.gsfc.nasa.gov>, thompson@serts.gsfc.nasa.gov (William Thompson) writes:
|> hevans@estwm0.wm.estec.esa.nl (Hugh Evans) writes:
|>
|> >I have discovered that after using Wave for an extended period that it slowly
|> >grabs more and more memory, even if new variables are not created, until
|> >finally it runs out of core memory. Whereas by saving the session and
|> >restarting it, the previous operation that crashed on a memory allocation
|> >problem will complete successfully.
|>
|>
|> It also strikes me that you could save the session, use .RNEW to clear out all
|> the memory, and restore it.
|>
But will this allow you to start up in the middle of a program?
i.e. can I Control-C a program; save,/all; save ,/routines; .RNEW;
and then restore everything and .continue from where I left off?
This is not an idle question. After a day carefully breaking up some
matrix calculations into 1-2 MB pieces that wouldn't stretch the memory of my
machine, a few hours into the run the sysadmin dropped by to warn me that
my process was taking up 30 megabytes! This really makes me wonder if there's
any way to deal with data sets that are larger than available memory.
Would it help if I cleared temporary variables and arrays every pass through
my main loops?
--
Elliotte Rusty Harold National Solar Observatory
eharold@sunspot.noao.edu Sunspot NM 88349
|
|
|