have a machine with 11.04 on it so I will give that a go later to see
what goes.
Thanks, Jeff
Message: 2 Date: Sun, 22 May 2011 12:32:43 -0500 From: Robert Kern
Subject: Re: [Numpy-discussion] Python memory
management issues using Linux. Maybe Numpy related. To: Discussion of
Numerical
goes.
Thanks, Jeff
Message: 2 Date: Sun, 22 May 2011 12:32:43 -0500 From: Robert Kern
Subject: Re: [Numpy-discussion] Python memory
management issues using Linux. Maybe Numpy related. To: Discussion of
Numerical Python Message-ID:
Content-Type:
text/plain; charset=UTF-8 On Sat, May 21
re are no
> issues.
>
> from numpy import arange, sum
>
> for x in range(1000):
> inhibVal = sum(arange(15))
>
> Cheers,
> Jeff
>
> Message: 3
> Date: Sun, 22 May 2011 09:32:10 -0500
> From: Bruce Southey
> Subject: Re: [Numpy-discussion] Python
On 05/22/2011 08:17 AM, Jeffrey Spencer wrote:
> from numpy import arange, sum
>
> for x in range(1000):
> inhibVal = sum(arange(15))
Memory usage stays constant with Ubuntu 11.04, 64-bit, using the numpy
1.5.1 package from ubuntu, and using 1.6.1.dev-a265004.
efiring@manini:~$ un
(1000):
inhibVal = sum(arange(15))
Cheers,
Jeff
Message: 3
Date: Sun, 22 May 2011 09:32:10 -0500
From: Bruce Southey
Subject: Re: [Numpy-discussion] Python memory management issues using
Linux. Maybe Numpy, related.
To: Discussion of Numerical Python
On Sat, May 21, 2011 at 23:27, Jeffrey Spencer wrote:
> I have had issues with Linux (Ubuntu 10.04 x86_64) not releasing memory
> back to the OS. I have code here the exhibits the issue:
>
> http://stackoverflow.com/questions/5975255/memory-allocated-to-python-in-the-os-is-never-released-back-in-l
Message: 3
Date: Sun, 22 May 2011 09:32:10 -0500
From: Bruce Southey
Subject: Re: [Numpy-discussion] Python memory management issues using
Linux. Maybe Numpy, related.
To: Discussion of Numerical Python
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1
On
Much reduced code exhibiting the issue. This shouldn't use much memory
but just keeps going up and up because the copied window I assume gets
left around and not taken up by the garbage collector.
On 22/05/11 23:42, Ralf Gommers wrote:
On Sun, May 22, 2011 at 2:54 PM, Jeffrey Spencer
mailto
On Sun, May 22, 2011 at 8:42 AM, Ralf Gommers
wrote:
>
>
> On Sun, May 22, 2011 at 2:54 PM, Jeffrey Spencer
> wrote:
>>
>> Sorry. I attached here the class and script to run it. It is just a
>> minimalistic example of what I'm really doing that exhibits the same
>> behavior. All the script does i
On Sun, May 22, 2011 at 2:54 PM, Jeffrey Spencer wrote:
> Sorry. I attached here the class and script to run it. It is just a
> minimalistic example of what I'm really doing that exhibits the same
> behavior. All the script does is run at.createSpecific after instantiating
> the class. I have seen
Sorry. I attached here the class and script to run it. It is just a
minimalistic example of what I'm really doing that exhibits the same
behavior. All the script does is run at.createSpecific after
instantiating the class. I have seen this exhibited on many other cases
but it runs fine in Windo
On Sun, May 22, 2011 at 6:27 AM, Jeffrey Spencer wrote:
> I have had issues with Linux (Ubuntu 10.04 x86_64) not releasing memory
> back to the OS. I have code here the exhibits the issue:
>
>
> http://stackoverflow.com/questions/5975255/memory-allocated-to-python-in-the-os-is-never-released-back-
I have had issues with Linux (Ubuntu 10.04 x86_64) not releasing memory
back to the OS. I have code here the exhibits the issue:
http://stackoverflow.com/questions/5975255/memory-allocated-to-python-in-the-os-is-never-released-back-in-linux-even-after-g
Then I read at http://pushingtheweb.com/20
13 matches
Mail list logo
