News for hackers. Stuff that matters.

A comment on When the memory allocator works against you. Parent comment

Re:When the memory allocator works against you by glandium on Sunday March 12, 2017 @06:42PM (#13853612)
Author here. The last graph actually shows that the problem still happens with CPython's allocator disabled.

Also, to clarify, the amount of memory allocated is actually decreasing (in-use bytes), while the memory allocator requests more and more memory from the system (system bytes), presumably because of fragmentation.

[ Parent | on HN ]
Re:When the memory allocator works against you by Kenji on Monday March 13, 2017 @03:16PM (#13861326)
>The last graph actually shows that the problem still happens with CPython's allocator disabled.

Excuse my ignorance, but couldn't it still be a problem of the python runtime? I.e. they use malloc wrong, etc?

[ Parent | on HN ]
Re:When the memory allocator works against you by malisper on Sunday March 12, 2017 @07:12PM (#13853843)
I see. I thought system bytes included the mmaped block of memory (the docs for malloc_stats explicitly say it does not) and I thought the last graph was a demonstration of why the Python memory allocator was necessary.
[ Parent | on HN ]