[issue26734] Repeated mmap\munmap calls during temporary allocation

Changes by Antoine Pitrou : -- resolution: -> duplicate status: open -> closed superseder: -> Use new madvise()'s MADV_FREE on the private heap ___ Python tracker ___ _

[issue26734] Repeated mmap\munmap calls during temporary allocation

STINNER Victor added the comment: FYI a discussion started in the issue #26601. -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs

[issue26734] Repeated mmap\munmap calls during temporary allocation

Changes by Brett Cannon : -- components: -Benchmarks ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue26734] Repeated mmap\munmap calls during temporary allocation

Changes by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue26734] Repeated mmap\munmap calls during temporary allocation

New submission from Bar Harel: After asking a question regarding performance in StackOverflow, I received an answer which seemed like a design problem in object allocation. This is the question: http://stackoverflow.com/q/36548518/1658617 Seems like it ignores the garbage allocation settings (as