{"id":1346,"date":"2018-01-19T19:22:44","date_gmt":"2018-01-19T19:22:44","guid":{"rendered":"http:\/\/goofy-trucks.flywheelsites.com\/profiling-php-code-with-xdebug-and-kcachegrind-page-2\/"},"modified":"2018-01-19T19:24:43","modified_gmt":"2018-01-19T19:24:43","slug":"profiling-php-code-with-xdebug-and-kcachegrind-page-2","status":"publish","type":"post","link":"https:\/\/phpbuilder.com\/profiling-php-code-with-xdebug-and-kcachegrind-page-2\/","title":{"rendered":"Profiling PHP Code with Xdebug and KCacheGrind Page 2"},"content":{"rendered":"
\n
\n
By W. Jason Gilmore<\/div>\n
on December 30, 2010<\/div>\n<\/p><\/div>\n
\n

Reviewing Performance Using the Source Code<\/h2>\n
KCacheGrind offers numerous ways to peer into your application’s performance, among them the ability to tie execution times directly to the source code. Figure 3 presents KCacheGrind’s annotated view of the profiled source code, prepending the execution time to each respective line.<\/div>\n

\n

Click here for larger image<\/em><\/font><\/a>
\n
Figure 3.<\/strong> Tying Execution Time to the Application Source Code<\/font><\/div>\n

Reviewing Call Graphs<\/h2>\n
Another interesting way to peer into your application’s execution cycle is via KCacheGrind’s Call Graph feature, an example of which is found in Figure 4. This graph not only traces the execution flow, but also associates call frequencies and the amount of total execution time required by each step in the cycle.<\/div>\n

\n

Click here for larger image<\/em><\/font><\/a>
\n
Figure 4.<\/strong> Reviewing a Zend Framework Action Call Graph<\/font><\/div>\n

Further Reading<\/h2>\n
Xdebug and KCacheGrind offer invaluable insight into application performance, not only presenting a comprehensive breakdown of the entire cycle’s execution time but also providing the ability to visually trace the execution path using a variety of tabular and flowchart-based views. Be sure to check out the following resources for more information about optimizing your PHP applications:<\/div>\n