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 kristjan.jonsson
Recipients Rhamphoryncus, amaury.forgeotdarc, barry, gregory.p.smith, jlaurila, jszakmeister, kristjan.jonsson, ncoghlan, neilo, pitrou, pjmcnerney, rhettinger, tlesher, vstinner
Date 2013-06-03.09:40:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370252422.26.0.0658971610211.issue3329@psf.upfronthosting.co.za>
In-reply-to
Content
Also, our ccpmem.h, the interface to the ccpmem.cpp, internal flexible memory allocator framework.
Again, just FYI.  There are no trade secrets here, so please ask me for more details, if interested.  One particular trick we have been using, which might be of interest, is to be able to tag each allocation with a "context" id.  This is then set according to a global sys.memcontext variable, which the program will modify according to what it is doing.  This can then be used to track memory usage by different parts of the program.
History
Date User Action Args
2013-06-03 09:40:22kristjan.jonssonsetrecipients: + kristjan.jonsson, barry, rhettinger, gregory.p.smith, amaury.forgeotdarc, ncoghlan, Rhamphoryncus, pitrou, vstinner, jszakmeister, tlesher, jlaurila, neilo, pjmcnerney
2013-06-03 09:40:22kristjan.jonssonsetmessageid: <1370252422.26.0.0658971610211.issue3329@psf.upfronthosting.co.za>
2013-06-03 09:40:22kristjan.jonssonlinkissue3329 messages
2013-06-03 09:40:22kristjan.jonssoncreate