This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients amaury.forgeotdarc, belopolsky, neologix, python-dev, rhettinger, tim.peters, vstinner
Date 2013-11-20.21:47:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384984026.11.0.622605088373.issue18874@psf.upfronthosting.co.za>
In-reply-to
Content
Charles-François doesn't like packed structure (frame_t) because he fears crash on architectures not supporting non-aligned memory access or bad performances. Antoine and me want them to reduce the memory footprint of the tracemalloc module (tracemalloc.get_tracemalloc_memory()).

I think that the memory footprint has an higher price than the performances for tracemalloc: I can wait longer for a result, whereas I may not be able to use tracemalloc if it uses too much memory.

I propose to pack frame_t structure, and only disable it explicitly on architectures where tracemalloc does crash. What do you think?
History
Date User Action Args
2013-11-20 21:47:06vstinnersetrecipients: + vstinner, tim.peters, rhettinger, amaury.forgeotdarc, belopolsky, neologix, python-dev
2013-11-20 21:47:06vstinnersetmessageid: <1384984026.11.0.622605088373.issue18874@psf.upfronthosting.co.za>
2013-11-20 21:47:06vstinnerlinkissue18874 messages
2013-11-20 21:47:05vstinnercreate