On Wed, Oct 29, 2008 at 8:33 AM, Gisle Aas <[EMAIL PROTECTED]> wrote: >>> Another idea would be to also >>> output >>> chunks about how much memory is allocated at different times. >> >> There's a note in HACKING about that: >> >> : Could optionally track resource usage per sub. Data sources could be >> : perl sv arenas (clone visit() function from sv.c) to measure number of >> : SVs & total SV memory, plus getrusage()). Abstract those into a >> : structure with functions to subtract the difference. Then use the same >> : logic to get inclusive and exclusive values as we use for inclusive and >> : exclusive subroutine times. >> >> That's potentially very powerful. > > It does seem much harder to isolate the effects of the program itself > from the effects of the profiler on stuff like this. I hope I'm wrong > about that.
Perhaps, but that shouldn't stop us from trying. NYTProf would be the first statement- or sub-based memory profiler for Perl. It's okay that there would be caveats in version 1. Shawn --~--~---------~--~----~------------~-------~--~----~ You've received this message because you are subscribed to the Devel::NYTProf Development User group. Group hosted at: http://groups.google.com/group/develnytprof-dev Project hosted at: http://perl-devel-nytprof.googlecode.com CPAN distribution: http://search.cpan.org/dist/Devel-NYTProf To post, email: [email protected] To unsubscribe, email: [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
