Re: Python memory handling
- From: Klaas <mike.klaas@xxxxxxxxx>
- Date: 31 May 2007 11:18:13 -0700
On May 31, 11:00 am, Thorsten Kampe <thors...@xxxxxxxxxxxxxxxx> wrote:
If it's swapped to disk than this is a big concern. If your Python app
allocates 600 MB of RAM and does not use 550 MB after one minute and
this unused memory gets into the page file then the Operating System
has to allocate and write 550 MB onto your hard disk. Big deal.
You have a long-running python process that allocates 550Mb of _small_
objects and then never again uses more than a tenth of that space?
This is an abstract corner case, and points more to a multi-process
design rather than a flaw in python.
The unbounded size of python's int/float freelists are slightly more
annoying problems, but nearly as trivial.
-Mike
.
- References:
- Python memory handling
- From: frederic . pica
- Re: Python memory handling
- From: Josh Bloom
- Re: Python memory handling
- From: frederic . pica
- Re: Python memory handling
- From: Chris Mellon
- Re: Python memory handling
- From: Thorsten Kampe
- Python memory handling
- Prev by Date: Standalone HTTP parser?
- Next by Date: Re: FAQ: how to vary the byte offset of a field of a ctypes.Structure
- Previous by thread: Re: Python memory handling
- Next by thread: Re: Python memory handling
- Index(es):
Relevant Pages
|