December 9, 2008 at 12:32Convenient profiling in Kcachegrind
discovered a nuclear feature when profiling with xdebug + kcachegrind) (for myself at least).
In general, you need to start the debugger and stop on the first line, then simultaneously load the file into kcachegrind, where xdebug gradually merges the result of profiling. Next, the debugger needs to be moved to the next. line, then click "reload" in kcachegrind and vaul). The profiling file is reloaded and the information is updated. The whole process of php, step by step, is literally visible as in the picture (call graph tab).
PS I think it makes sense to fasten the animation to this matter and then the development process will generally be comparable to watching the series)
PSPS the kcachegrind cache error (as I understand it) was a negative point, which was decided by adjusting the configuration files in the home folder.
Tested for:
Linux OS
Kcachegrind 0.4.6
Eclipse (PDT)
xdebug 2.0.0-2
In general, you need to start the debugger and stop on the first line, then simultaneously load the file into kcachegrind, where xdebug gradually merges the result of profiling. Next, the debugger needs to be moved to the next. line, then click "reload" in kcachegrind and vaul). The profiling file is reloaded and the information is updated. The whole process of php, step by step, is literally visible as in the picture (call graph tab).
PS I think it makes sense to fasten the animation to this matter and then the development process will generally be comparable to watching the series)
PSPS the kcachegrind cache error (as I understand it) was a negative point, which was decided by adjusting the configuration files in the home folder.
Tested for:
Linux OS
Kcachegrind 0.4.6
Eclipse (PDT)
xdebug 2.0.0-2