ActiveState Powered by ActiveState

ActiveState Community


XDebug Code Profiling

Posted by Nycto on 2007-10-04 10:09
OS: All / Any

I was about to install xdebug on my server this morning to profile some code when I realized that Komodo uses it for PHP debugging. I checked my debug php.ini file and saw the code profiler was not enabled. I threw the following lines in to the ini file:

xdebug.profiler_enable=1
xdebug.profiler_output_dir=/dir/tree/to/Komodo-IDE-4.2/php/xdebug
xdebug.profiler_output_name=cachegrind.out.%s

and profiling worked without a hitch. I then noticed that if I added a breakpoint to a script, the cachegrind file contained live data when the script paused execution.

Are there plans to integrate the profiling functionality of xdebug in to Komodo? If not, is anyone working on an extension? It seems like a fairly logical step.

Re: profiling
ToddW | Thu, 2007-10-04 10:31

Thanks for adding your findings about the PHP Xdebug profiling.

There has been discussions in the Komodo team about adding profiling support into Komodo (no time frame yet) so it may happen sometime down the road...

That is interesting that the Xdebug profiler counts breakpoint stoppage time, I'd log a bug for that with Xdebug:
http://bugs.xdebug.org/

Cheers,
Todd

Is there any news on this?
bopp | Wed, 2008-04-23 11:19

Is there any news on this? The only reason i keep my old Zend installed, is that i sometimes need the profiler to see what's causing bottlenecks.

It would be great if Komodo added Profiling functionality.

Re: profiling update
ToddW | Thu, 2008-04-24 14:06

No updates yet. This will likely be examined/scheduled/scoped by the Komodo team as part of upcoming Komodo 5 planning.

KCachegrind
dis.pater | Fri, 2008-04-25 02:06

Why don't yyou use KCachegrind to analyze your profiling data?
IMHO this is way better than the "gui" provided by Zend.

-->