Convenient profiling in Kcachegrind
discovered the 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 profiling result. Next, you need to move the debugger to the next. line, then click "reload" in kcachegrind and wahl). 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 (tab call graph).
PS I think it makes sense to tie the animation to this case, and then the development process will generally be comparable to watching the series)
PSPS negative was the cache error kcachegrind (as I understood it), which was decided by adjusting the configuration files in the home folder.
Checked on:
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 profiling result. Next, you need to move the debugger to the next. line, then click "reload" in kcachegrind and wahl). 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 (tab call graph).
PS I think it makes sense to tie the animation to this case, and then the development process will generally be comparable to watching the series)
PSPS negative was the cache error kcachegrind (as I understood it), which was decided by adjusting the configuration files in the home folder.
Checked on:
Linux OS
Kcachegrind 0.4.6
Eclipse (PDT)
xdebug 2.0.0-2
')
Source: https://habr.com/ru/post/46504/
All Articles