Repeated mmap\munmap calls during temporary allocation

[bharel]

BPO	26734
Nosy	@pitrou, @vstinner, @bharel
Superseder	bpo-26601: Use new madvise()'s MADV_FREE on the private heap

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2016-04-11.17:33:15.655>
created_at = <Date 2016-04-11.16:50:01.962>
labels = ['interpreter-core', 'tests', 'performance']
title = 'Repeated mmap\\munmap calls during temporary allocation'
updated_at = <Date 2016-04-11.17:33:15.654>
user = 'https://github.com/bharel'

bugs.python.org fields:

activity = <Date 2016-04-11.17:33:15.654>
actor = 'pitrou'
assignee = 'none'
closed = True
closed_date = <Date 2016-04-11.17:33:15.655>
closer = 'pitrou'
components = ['Interpreter Core', 'Tests']
creation = <Date 2016-04-11.16:50:01.962>
creator = 'bar.harel'
dependencies = []
files = []
hgrepos = []
issue_num = 26734
keywords = []
message_count = 2.0
messages = ['263189', '263190']
nosy_count = 3.0
nosy_names = ['pitrou', 'vstinner', 'bar.harel']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = '26601'
type = 'performance'
url = 'https://bugs.python.org/issue26734'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3', 'Python 3.4', 'Python 3.5', 'Python 3.6']

[bharel]

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 timeit is supposed to disable it as far as I know) and I might not be proficient in low-level programming but there should be a way to implement it that doesn't cause endless allocations.

[vstinner]

FYI a discussion started in the issue bpo-26601.