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 kristjan.jonsson
Recipients kristjan.jonsson
Date 2012-03-29.09:54:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333014849.93.0.173252206175.issue14435@psf.upfronthosting.co.za>
In-reply-to
Content
floatobject.c has its own block allocator.  This appears to be ancient, from before the time when obmalloc.c was invented.
This patch removes this allocator and puts an upper limit on the freelist of floats.  The purpose of this is to reduce memory fragmentation, since blocks used for floats cannot be used for anything else in python.  These blocks tend to stay around for a long time, it is sufficient for one float from each of the 1k blocks to be alive to keep that block present in memory forever.

It is the presence of the fast freelist that is the performance enhancer here, not the fast block allocator.
History
Date User Action Args
2012-03-29 09:54:10kristjan.jonssonsetrecipients: + kristjan.jonsson
2012-03-29 09:54:09kristjan.jonssonsetmessageid: <1333014849.93.0.173252206175.issue14435@psf.upfronthosting.co.za>
2012-03-29 09:54:09kristjan.jonssonlinkissue14435 messages
2012-03-29 09:54:09kristjan.jonssoncreate