On Aug 25, 2:08 am, Chris Withers ch...@simplistix.co.uk wrote:
Martin v. Löwis wrote:
Today, there are two cases when malloc returns memory on a typical
Unix system (in particular, in Linux malloc):
a) if the malloc block block is small (below page size), it is allocated
from the brk
Martin v. Löwis wrote:
Today, there are two cases when malloc returns memory on a typical
Unix system (in particular, in Linux malloc):
a) if the malloc block block is small (below page size), it is allocated
from the brk heap, where it can only be returned if the last page of
that heap is
As far as releasing memory back to the OS is concerned, I have dim
memories of *x systems where free() would return space to the OS if
the block was large and it was next to the break point ... this
effect could be what you are seeing.
Today, there are two cases when malloc returns memory on
On Aug 15, 7:55 am, Chris Withers ch...@simplistix.co.uk wrote:
Hi All,
I thought this was fixed back in Python 2.5, but I guess not?
So, I'm playing in an interactive session:
from xlrd import open_workbook
b = open_workbook('some.xls',pickleable=0,formatting_info=1)
At this point,
Hi All,
I thought this was fixed back in Python 2.5, but I guess not?
So, I'm playing in an interactive session:
from xlrd import open_workbook
b = open_workbook('some.xls',pickleable=0,formatting_info=1)
At this point, top shows the process usage for python to be about 500Mb.
That's okay,
Chris Withers wrote:
div class=moz-text-flowed style=font-family: -moz-fixedHi All,
I thought this was fixed back in Python 2.5, but I guess not?
So, I'm playing in an interactive session:
from xlrd import open_workbook
b = open_workbook('some.xls',pickleable=0,formatting_info=1)
At this
On Aug 15, 12:55 pm, Chris Withers ch...@simplistix.co.uk wrote:
Hi All,
I thought this was fixed back in Python 2.5, but I guess not?
So, I'm playing in an interactive session:
from xlrd import open_workbook
b = open_workbook('some.xls',pickleable=0,formatting_info=1)
At this point,
Mark Dickinson wrote:
and got the expected memory usage for my Python process, as
displayed by top: memory usage went up to nearly 1Gb after
each assignment to b, then dropped down to 19 Mb or so after
each 'del b'. I get similar results under Python 2.5.
I get the same results on Linux:
On Aug 16, 2:41 am, Mark Dickinson dicki...@gmail.com wrote:
and got the expected memory usage for my Python process, as
displayed by top: memory usage went up to nearly 1Gb after
each assignment to b, then dropped down to 19 Mb or so after
each 'del b'. I get similar results under Python
