PhpStorm 6.0.1 Web Help

When integration with the Zend Debugger profiler is enabled, PhpStorm provides visual representation of profiler snapshots. PhpStorm opens a separate editor tab with four views where the data are presented based on different criteria.

With Zend Debugger, profiling is supported within a zero configuration debugging session.

To have the profiling data collected and analyze it, perform these general steps:

To initiate a debugging session
  1. Enable control over the debugger from the browser.
  2. Generate bookmarklets to toggle the debugger through.
  3. Toggle the Start Listen PHP Debug Connections button start_listening_php_debug_connections.png so it changes its color to green stop_listening_php_debug_connections.png. After that PhpStorm starts listening to the port of the debugging engine used in the current project. Ports for debuggers are set at the PhpStorm level in the Debug dialog box (File | Settings | PHP | Debug for Windows and Linux, PhpStorm | Preferences | PHP | Debug for Mac OS).
  4. Open the starting page of your application in the browser.
  5. To activate Zend Debugger from the browser, choose the Zend Start Profilerbookmark.
  6. Refresh the page.
  7. Return to PhpStorm.
  8. In the dialog box, that opens, select the incoming connection to profile and click Accept.

    Note

    The Incoming Connection from Zend Debugger dialog box appears only once, when you accept connection from this host for the first time.

    PhpStorm presents the collected profiling data in a separate editor tab with the name of the selected profiler output file.

To view and examine the profiling data, perform these general steps

When you request on the accumulated profiling data, PhpStorm opens its visualized presentation in a separate editor tab. The tab is named after the file that implements the page you are currently profiling and consists of several views. Switch between the views to analyze the profiling data based on various criteria of analysis.

  • In the Execution Statistics view, examine the summary information about execution metrics of every called function.
  • In the Call Tree view, explore the execution paths of all called functions.
  • To explore the execution paths of a specific function, select the function in question in the Call Tree view and view its callees in the Callees view.
  • To explore all the paths that can result in calling a specific function, select the function in question in the Call Tree view and examine its possible callers in the Callers view.

See Also

Procedures:

Web Resources: