This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sable
Recipients BreamoreBoy, loewis, pitrou, sable, tim.peters
Date 2010-07-23.09:38:20
SpamBayes Score 0.029787568
Marked as misclassified No
Message-id <>
Well I am still interested in getting this patch officially integrated in Python.

This patch is integrated in the version of Python that we deploy to our customers with our products (Sungard GP3). So it runs in production at various clients sites (some European banks with massive SunOs and AIX servers running thousands of sessions of our application) and it has provided some huge memory consumption improvements.

The problem appears quite obviously when you run a relatively big application on SunOS or AIX: if you allocate some memory in a Python process at some stage, this memory will never be released to the system until you leave that process, even if that memory is not used by Python anymore.
With my patch, the process can actually release the memory to the system so that it can be used by other processes.

Linux is not impacted by this problem because the GNU libc implements the same memory allocation mechanism based on dlmalloc.

I guess there are not that many people running Python applications with a big memory footprint on AIX or SunOS, otherwise this problem would be more popular.
Date User Action Args
2010-07-23 09:38:23sablesetrecipients: + sable, tim.peters, loewis, pitrou, BreamoreBoy
2010-07-23 09:38:22sablesetmessageid: <>
2010-07-23 09:38:21sablelinkissue3526 messages
2010-07-23 09:38:20sablecreate