Hello, I've had a closer look at Heapy. In general it seems it would do the job - weren't it for the fact it is unable to track memory consumed by C extensions. At least in our case the extensions in questions are ours so we could in principle modify them to give Heapy all the necessary information (for more information on this see the "Extra stuff for c extension developers" section at http://www.pkgcore.org/trac/pkgcore/doc/dev-notes/heapy.rst), then again it may be too much of a hassle.
Another option would be to run our tests through a binary-level profiler like the one offered by the Valgrind suite. Unfortunately this SIGNIFICANTLY increases execution time (by a factor of over 10, AFAIK) and is therefore out of the question in case of megatests. Looks like we may be the best off simply periodically calling 'ps' or querying the /proc directory. Cheers, -- MS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
