> Start using webgrind with your browser of choice. <

How ?

Maybe the authors are a little too close to it, but for the uninitiated a little elaboration and an example would be most helpful ... and maybe contribute to more widespread use.

does it requires specific Xcode settings? I can select cachegrind file but I got always blank page on output.

How do you use it???? why is it such a secret?? I can't find help on using this anywhere

You need to get xdebug to generate cachegrind files first. Once you can get Xdebug to generate cache grinds, you can look at them. For me it found the grind files automatically.

This worked out of the box for me on osx leopard using mamp. My xdebug cachegrind files are in '/xdebug-profiling' and I set that folder in the webgrind config file as the 'storageDir'. I'm not sure if this is needed though.

Problems like the above may be caused by a php version lower than 5.2 and/or the lack of json_encode support...

And for the people who don't get the 'start using webgrind with your browser of choice': if you put your webgrind folder in your server root, then point your browser to http://localhost/webgrind, select a file in the dropdown menu in the top right corner and click 'update' and you're done. All the nice stats should show up in your browser :)

To enable xdebug profiler you need to put "xdebug.profiler_enable=1" to your php.ini.

In MAMP, I first had to disable the zend optimizer ... not sure if that was enabled out of the box or not because my MAMP build has gotten pretty hacked up in the past year since MAMP 1.7 came out.

You need a .htaccess file in the directory for webgrind and where your app is with this:

php_flag xdebug.profiler_enable 1
php_value xdebug.profiler_output_dir /full/path/to/save/grindfiles 
php_value xdebug.profiler_output_name cachegrind.out.%t.%p

The problem I found was that webgrind assumes this is set for its own directory and that the php values for profiler_output_dir and profiler_output_name are set. The script needs an easy override command for the output directory and output name format in the config.php file.

I dont know how to use it.

Could you post a more detailed installation instructions please ?

Unable to make it work on a windows XAMPP install. The Xdebug trace shows that webgrind finds the profiling dumps and prepares to show them, but the web page doesn't have anything on it...

Just posted an article on installing and configuring webgrind here: http://www.chrisabernethy.com/php-profiling-xdebug-webgrind/

I found that one of the issues is making sure to specify a value for xdebug.profiler_output_name that wouldn't cause the file to be overwritten each time you serve a page from the same Apache process (the value defaults to using PID as a unique identifier).

Hello, I try to make it works on a debian server and i just achieve to profile the code of webgrind itself, how can i profile other script which are located at the same root level directory ... ?

thx

Hi, I made it to work with the following configuration in both /apache/bin/php.ini AND /php/php.ini:

zend_extension_ts="\path\to\ext\php_xdebug.dll"
xdebug.remote_enable=true
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
xdebug.remote_handler=dbgp
xdebug.profiler_enable=1
xdebug.profiler_output_name = cachegrind.out.%t.%p
xdebug.profiler_output_dir="C:\xampp\tmp"

For full guide on how to install webgrind + xdebug go here: http://anantgarg.com/2009/03/10/php-xdebug-webgrind-installation/

In wich section of php.ini must be written this line : xdebug.profiler_enable = 1 At the end of the php.ini file ?

@angelo.rigo:

It doesn't matter where in the php.ini file you put the xdebug enabling line. Please refer to the documentation for xdebug for further instructions on how to set it up: http://xdebug.org/docs/

Is xdebug listed on the phpinfo function ? or the way i can see the extension is enabled is looking at the php.ini file ?

@angelo.rigo:

Yes, the xdebug extension will appear in the output of phpinfo() as a separate section with version information.

>The Xdebug trace shows that webgrind finds the profiling dumps and prepares to >show them, but the web page doesn't have anything on it...

Please note that webgrind (at least v 1.0) needs function "json_encode". It is a built-in function since PHP >= 5.2.0. Otherwise you shoud install it manually: http://pecl.php.net/package/json For example, use "pecl install json" and it will produce json.so module

Couldn't get this going until I used

xdebug.profiler_output_name = "cachegrind.out.%t.%p"

Looks nice otherwise! :)

SO, keep in mind that if you have changed the xdebug.profile_output_name to not include a pid then webgrind will not find your profiles. The reason is because it excludes its own cachegrind profiles on purpose to avoid infinite loop.