search

gajus / xhprof.io

GUI to analyze the profiling data collected using XHProf – A Hierarchical Profiler for PHP.
http://xhprof.io/
Other
429 stars 103 forks source link

Full call tree / backtrace, as in xdebug profiler + wincachegrind? #68

Open donquixote opened 9 years ago

donquixote commented 9 years ago

I am used to profiling with xdebug, and then use wincachegrind (on wine) to look at the results (I prefer wincachegrind to kcachegrind). The output from xdebug allows to really inspect the complete call tree. This can be quite hairy big data for long processes, but I find it super useful. I don't really care about visual representation, I am happy to click through the list to explore the call tree.

Now everyone is telling me to use xhprof instead.

It seems that xhprof does not really distinguish between functions and calls, and does not record a full call tree. It only remembers how often function A calls function B, but not anything about the call trace, or which call instance of A calls which call instance of B.

Is this a correct observation? Would it be possible to implement the full call tree capture in xhprof? Thanks!

donquixote commented 9 years ago

Maybe to avoid crazy big output files, it would be an option to group calls by their stack trace.