Differences between revisions 1 and 2
Revision 1 as of 2008-02-10 21:44:31
Size: 697
Editor: www-gw4
Comment:
Revision 2 as of 2008-02-10 21:48:22
Size: 963
Editor: www-gw4
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * [http://groups.google.com/group/trac-dev/browse_thread/thread/116e519da54f16b difficulties to find a leak in Edgewall Trac]
 * [http://wingolog.org/archives/2007/11/27/reducing-the-footprint-of-python-applications reducing the footpring of python applications]

As Christian Heimes describes it [http://groups.google.com/group/comp.lang.python/browse_thread/thread/32e62acc62773a3d#d9baaa3a229ad90b here], Python uses its own memory allocator for small objecst (< 257 bytes). Larger objects are allocated directly with malloc, smaller objects end up in arenas. The code is well documented [http://svn.python.org/view/python/trunk/Objects/obmalloc.c?rev=56476&view=auto in obmalloc.c].

Related information:

FreeMemory (last edited 2010-11-27 04:19:23 by adsl-074-166-103-084)

Unable to edit the page? See the FrontPage for instructions.