The following procedure demonstrates how to profile a PHP Script, either locally or remotely:
Create a file, called Person, and copy-paste the example code into it. (Click here for the example code)
Create a second file, called tryPerson, and copy-paste the example code into it. (Click here for the example code).
Save both files.
Click the arrow next to the Profile button
on the toolbar and select Profile Configurations...
-or- from the main menu go to Run | Profile Configurations... -or- right-click
in PHP Explorer view and select Profile Configurations....A Profile dialog will appear.
Double-click the PHP Script option to create a new Profile configuration.
Enter a name for the new configuration.
To profile the file locally using Zend Studio's internal debugger, select the PHP Executable setting under the Debugger Location category and select the required PHP executable (PHP 4 or 5).
To profile the file remotely on your server using the Zend Debugger installed on your server, select the PHP Web Server option and select your server from the drop-down list. (If you have not yet configured a server, click the PHP Servers link and follow the instructions under Adding PHP Servers.)Under PHP File, click Browse and select the "TryPerson" file.
Click Apply and then Profile.
A confirmation dialog will be displayed asking whether you want to open the Profiling Perspective.
Click Yes. (If you would like the Profiling Perspective to open by default in the future, mark the 'Remember my decision' checkbox.)
The Profiling Perspective will open, displaying the Profiling Monitor window with the following information:
Profiler Information - provides general information on the profiling duration and date, number of files constructing the requested URL and more. In addition, it displays a Time Division Pie Chart for the files in the URL.
The right side displays time division in a pie chart and the left side provides the following information:URL - The URL analyzed
Query - The specific query parameters
Path - The exact location of the first file called
Total Request Time - Total process time of the entire page
Number of Files - Number of files composing the page
Date - Date and time that the profiling took place
Execution Statistics - Displays the list of files constructing the URL and detailed information on functions in the files. The window contains statistics relevant to each function:
Function - The name and location of the function.
Calls Count - The number of times that the function was called.
Average Own Time - The average duration without internal calls.
Own Time(s) - The net process duration without internal calls.
Others Time(s) - Time spent on calling other files.
Total Time(s) - The total process duration including internal calls.
Note:
Click the 'Show as percentage' button on the toolbar to see the statistics as percentages rather than times.
Execution Flow - Shows the flow of the execution process and summarizes percentages and times spent on each function.
Function - Function name
File - The file in which the function is located
Total Execution Time - Percent of time taken per function.
Duration Time - Time taken per function. In milliseconds.
Code Coverage Summary - Summary of how many lines of code were covered.
Element - The file / folder that was called.
Covered Lines (Visited / Significant / Total) - Percentage of lines covered within each file. (Visited = Number of lines covered / Significant = number of lines excluding comments and declarations/ Total = Total number of lines in the file.)
Clicking on the 'Covered lines' percentages will open an editor containing the debug file, with the covered lines highlighted:
