Re: Memory problems with PyNio

Hi Jesper and Pavel,

Jesper is correct that a fairly serious memory leak (discovered by
him) has
recently been fixed in PyNIO. We can provide new builds for anyone
that
is adversely affected by this.
  -dave

On Apr 17, 2007, at 7:14 AM, Jesper Larsen wrote:

> On Tuesday 17 April 2007 14:42, Pavel Jurus wrote:
>> I have problems when working with the large number of netcdf files. I
>> can
>> easily run out of memory - when I tried to optimize PyNgl scripts to
>> use
>> less memory, I found potential memory leak. Here is minimal example:
> <snip>
>> Shape of the float array 'result' is (1, 30, 114, 165), so
>> it should use around 30*114*165*4 ~ 2.25MB memory. Repeating
>> assignment
>> 100 times leads to python process using more than 225MB memory with
>> no way
>> to reuse this memory.
>
> Hi Pavel,
>
> I had the same problem a while ago. It turned out to be a memory leak
> in PyNIO
> (only in the Numeric version - the numpy version does not seem to have
> this
> problem). I recently got an updated build of PyNGL in which the leak
> was
> fixed but it does not seem to have made its way to the official
> download
> repository yet. Mary Haley might be able to provide more information
> on this?
>
> My own inquiry was actually not about a memory leak - but whether
> there is
> intentional RAM caching of data in PyNIO.
>
> Cheers,
> Jesper
> _______________________________________________
> pyngl-talk mailing list
> pyngl-talk_at_ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/pyngl-talk

_______________________________________________
pyngl-talk mailing list
pyngl-talk_at_ucar.edu
http://mailman.ucar.edu/mailman/listinfo/pyngl-talk
Received on Tue Apr 17 2007 - 11:45:10 MDT