[issue22222] dtoa.c: remove custom memory allocator

STINNER Victor added the comment: I was no aware of the performance degradation when I created the issue. 18 KB of memory is too low to invest effort on optimizing the generic Python memory allocator, I prefer to keep the heavily optimized allocator in dtoa.c. -- resolution: -> not a

[issue22222] dtoa.c: remove custom memory allocator

STINNER Victor added the comment: > A modified version of telco.py (using floats instead of decimals) > runs about 5-6% slower with the change here. Would it be possible to optimize the pymalloc allocator to reduce this slow-down? -- ___ Python trac

[issue22222] dtoa.c: remove custom memory allocator

Changes by Eric V. Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue22222] dtoa.c: remove custom memory allocator

Stefan Krah added the comment: A modified version of telco.py (using floats instead of decimals) runs about 5-6% slower with the change here. -- ___ Python tracker ___ __

[issue22222] dtoa.c: remove custom memory allocator

Serhiy Storchaka added the comment: This is very dangerous change. Could you please compare results of Python benchmarks with and without the patch? -- nosy: +pitrou, serhiy.storchaka ___ Python tracker __

[issue22222] dtoa.c: remove custom memory allocator

New submission from STINNER Victor: dtoa.c has an optimized memory allocator for performances: it uses a short pool of 2304 doubles (18 KB) to avoid calling malloc/free. Comment in dtoa.c: /* Memory management: memory is allocated from, and returned to, Kmax+1 pools of memory, where pool k (