classification
Title: Repeated mmap\munmap calls during temporary allocation
Type: performance Stage:
Components: Interpreter Core, Tests Versions: Python 3.6, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 2.7
process
Status: closed Resolution: duplicate
Dependencies: Superseder: Use new madvise()'s MADV_FREE on the private heap
View: 26601
Assigned To: Nosy List: bar.harel, pitrou, vstinner
Priority: normal Keywords:

Created on 2016-04-11 16:50 by bar.harel, last changed 2016-04-11 17:33 by pitrou. This issue is now closed.

Messages (2)
msg263189 - (view) Author: Bar Harel (bar.harel) * Date: 2016-04-11 16:50
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.
msg263190 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2016-04-11 17:11
FYI a discussion started in the issue #26601.
History
Date User Action Args
2016-04-11 17:33:15pitrousetstatus: open -> closed
superseder: Use new madvise()'s MADV_FREE on the private heap
resolution: duplicate
2016-04-11 17:11:14vstinnersetnosy: + vstinner
messages: + msg263190
2016-04-11 17:01:38brett.cannonsetcomponents: - Benchmarks
2016-04-11 17:01:12brett.cannonsetnosy: - brett.cannon
2016-04-11 16:50:02bar.harelcreate