> > The API isn't very stable or documented, as you've discovered. > The best general approach is to find where the information you want > is displayed in the nytprofhtml report and then look at the code > that implements that part of the report. > > For example, subroutine_table(), when called with no $fi arg, iterates > over all the subs, and report_src_line() has code that iterates over > all the callers to subs defined on a line and all the calls made to subs > by a line. See also bin/nytprofcg. >
Those should get you started. > > Thank you, these are a good starting point! A problem I see is that we would like to have the method calls from top to bottom, i.e. starting from Main going down to some application code (we are profiling catalyst-applications). I have not yet found a place in a report where this is done: subroutine_table: I think it contains aggregate info on all times the method was called. Is that correct or are the data aggregated in the function? (Sorry, I don't understand all the PERL in there :-) callgraph: It does not start from the top, i.e. main, it just adds edges and lets graphviz figure that out. cg: Does not know the top method, that has to be inferred from caller info To get a top-down printout of sub call, do I maybe have to use nytprofcalls? Or is there another place where this is done, that I overlook/misunderstood? Regards, Holger Have fun! > Tim. > -- -- 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] --- You received this message because you are subscribed to the Google Groups "Devel::NYTProf Dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
