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 jtaylor
Recipients StyXman, bar.harel, dw, jtaylor, neologix, pitrou, vstinner, ztane
Date 2016-04-22.11:24:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461324242.98.0.116944646741.issue26601@psf.upfronthosting.co.za>
In-reply-to
Content
I know one can change the allocator, but the default is mmap which I don't think is a very good choice for the current arena size.
All the arguments about fragmentation and memory space also apply to pythons arena allocator itself and I am not convinced that fragmentation of the libc allocator is a real problem for python as pythons allocation pattern is very well behaved _due_ to its own arena allocator. I don't doubt it but I think it would be very valuable to document the actual real world use case that triggered this change, just to avoid people stumbling over this again and again.

But then I also don't think that anything needs to be necessarily be changed either, I have not seen the mmaps being a problem in any profiles of applications I work with.
History
Date User Action Args
2016-04-22 11:24:03jtaylorsetrecipients: + jtaylor, pitrou, vstinner, StyXman, neologix, dw, ztane, bar.harel
2016-04-22 11:24:02jtaylorsetmessageid: <1461324242.98.0.116944646741.issue26601@psf.upfronthosting.co.za>
2016-04-22 11:24:02jtaylorlinkissue26601 messages
2016-04-22 11:24:02jtaylorcreate