Note: Xdebug, and in particular its profiling features, are very resource intensive and slow down PHP execution. Where is the application spending most of its time? the best payoff in performance tuning is focusing on those parts of the application which consume the most time. For functions that process and query data these could be prime opportunities for your application to cache.
KCachegrind, for example, will display information including: PHPStorm, a popular PHP IDE, can also display this profiling data. Once written the profile cache can be read by an application such as KCachegrind or Webgrind. Therefore when profiling it is sometimes easier to run curl to POST a form directly. The XDEBUG_PROFILE parameter will need to be passed into the subsequent POST request to analyze the second request which processes the form. So, for example, if you wish to analyze a form post, one profile will be written for the GET request to display the HTML form. Note that it will write one file for each PHP request / process that is executed. This is configurable with the xdebug.profiler_output_name setting. Īs the page processes it will write to a file with a name similar to /tmp/cachegrind.out.12345īy default the number in the filename is the process id which wrote it.
Next use a web client to make a request to your application's URL you wish to profile, e.g. Xdebug.profiler_output_name = "cachegrind.out.%p" # Output cachegrind files to /tmp so our system cleans them up later Xdebug.profiler_enable_trigger_value = "" # The GET/POST value we will pass empty for any value # Let's use a GET/POST parameter to turn on the profiler # Set to 1 to turn it on for every request This allows us to keep settings static and turn on the profiler only as needed. In our example we will run the profile optionally based on a request parameter. Some Linux distributions come with standard packages (e.g.
#PHP CODE PROFILER INSTALL#
To enable profiling, install the extension and adjust php.ini settings. No application code changes are necessary to perform this profiling. Applications are available on each platform to analyze these files.
When running the profiler, the output is written to a file in a binary format called "cachegrind". Profiling with XDebugĪn extension to PHP called Xdebug is available to assist in profiling PHP applications, as well as runtime debugging. Mysql_close() //close database connectionĬross posting my reference from SO Documentation beta which is going offline. $select_query = "SELECT * FROM data_table" Here is an example, calling prof_flag() with a description at each checkpoint, and prof_print() at the end: prof_flag("Start") Call this when you're done and want to see the resultsĮcho sprintf(" %f", $prof_timing-$prof_timing) Call this at each point of interest, passing a descriptive string No extensions are needed, just use these two functions for simple profiling.
0 kommentar(er)
