From help-octave-request at bevo dot che dot wisc dot edu Tue Jan  7 17:20:11 2003
Subject: Re: Memory usage
From: David Doolin <doolin at alpha-1 dot CE dot Berkeley dot EDU>
To: david dot pruitt at ashdonanalysis dot com
cc: Octave <help-octave at bevo dot che dot wisc dot edu>
Date: Tue, 7 Jan 2003 15:15:22 -0800 (PST)



One way is to write a c++ wrapper for your function, 
then use valgrind to examine the memory.  You can 
find valgrind using google.


On Tue, 7 Jan 2003, David Pruitt wrote:

> I have an octave program that calls many self-written functions as well as
> octave functions.  The program consumes a very large chunk of memory -
> (~750MB, many times more than I can rationalize based on the matrix sizes).
> The code runs over several minutes and the memory usage grows nearly
> linearly over time.  I'm guessing that memory is not being released as data
> are passed to and from functions.  
> 
>  
> 
> My questions:  
> 
>  
> 
> 1.	Is there some clever way to track the memory consumption with
> greater detail?
> 2.	Must I compel octave to release memory on return from a function?
> If so, how?
> 
>  
> 
>  
> 
> Thanks in advance.
> 
>  
> 
>  
> 
> David Pruitt, PhD
> 
> Ashdon Investment Analysis and Reseach, LLC
> 
> Phone: 931.695.3220
> 
> Mobile: 931.639.2477
> 
> Fax: 931.695.5545
> 
> e-mail: david dot pruitt at ashdonanalysis dot com
> 
>  
> 
> 



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------