Message 191506 - Python tracker

➜

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	vstinner
Recipients	brian.curtin, giampaolo.rodola, loewis, neologix, pitrou, tim.golden, trent, vstinner
Date	2013年06月20日.08:45:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAMpsgwb-kbXFFyWSDmzbpGx5ukDPKxzKbHtKcZxQzGb_57SUFA@mail.gmail.com>
In-reply-to	<1371716696.84.0.87003276337.issue13483@psf.upfronthosting.co.za>

Content
>> I plan to test the Low Fragmentation Allocator, at least on Windows 7. > I don't think it can be any better than raw mmap() / VirtualAlloc()... I mean using the Low Fragmentation Allocator for PyObject_Malloc() instead of pymalloc. Martin wrote (msg148605): "As an alternative approach, Python could consider completely dropping obmalloc on Windows, and using a Windows Low Fragementation Heap (LFH) instead, with HEAP_NO_SERIALIZE (as the heap would be protected by the GIL)."

Content

>> I plan to test the Low Fragmentation Allocator, at least on Windows 7.
> I don't think it can be any better than raw mmap() / VirtualAlloc()...
I mean using the Low Fragmentation Allocator for PyObject_Malloc()
instead of pymalloc.
Martin wrote (msg148605):
"As an alternative approach, Python could consider completely dropping
obmalloc on Windows, and using a Windows Low Fragementation Heap (LFH)
instead, with HEAP_NO_SERIALIZE (as the heap would be protected by the
GIL)."

History
Date	User	Action	Args
2013年06月20日 08:45:06	vstinner	set	recipients: + vstinner, loewis, pitrou, giampaolo.rodola, tim.golden, trent, brian.curtin, neologix
2013年06月20日 08:45:06	vstinner	link	issue13483 messages
2013年06月20日 08:45:05	vstinner	create

homepage