On Aug 25, 2:08 am, Chris Withers 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 heap, where it
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
On Aug 15, 7:55 am, Chris Withers 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, top sho
> 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 mem
On Aug 16, 2:41 am, 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.
>
> So maybe
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:
Pyt
On Aug 15, 12:55 pm, Chris Withers 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, top sh
Chris Withers 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, top shows the process usage for python to be
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 o
