https://docs.moodle.org/dev/api.php?action=feedcontributions&feedformat=atom&user=Harryf 2026-06-23T03:56:45Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/dev/index.php?title=Profiling_PHP&diff=18465 2010-11-10T20:24:55Z

<p>Harryf: </p> <hr /> <div>PHP has two significant profilers...<br /> <br /> One is [http://www.xdebug.org/docs/profiler XDebug] - this is well known and understood and it's trace output is supported by tools like [http://kcachegrind.sourceforge.net/html/Home.html KCachegrind].<br /> <br /> The other is [http://pecl.php.net/package/xhprof xhprof], a profiler released by facebook's engineering team, designed for capturing profile traces on live servers. Compared to XDebug, xhprof aims to have the minimum impact on execution times and require relatively little space to store a trace, so you can run it live without a noticeable impact on users and without filling disks. The trade off with xhprof is in ''slightly'' less detail and a trace format that needs it's own GUI to visualize (which ships with xhprof). The reason you'd want to profile in a live environments (vs. on development) is certain categories of problem may only been seen live, e.g. (data related) what happens when the user table grows 100 times, the impact on &quot;login.php&quot; or (service related) server to server HTTP requests. Did a presentation once [https://docs.google.com/present/view?id=dcbkgbgf_45fbg3rnmk XHProf - facebooks PHP profiler] which explains in more detail - Penny saw the talk which is how I ended up writing this.<br /> <br /> ==See also==<br /> <br /> * [http://moodle.org/mod/forum/discuss.php?d=162045 Forum thread about profiling Moodle 2.0]<br /> * [https://docs.google.com/present/view?id=dcbkgbgf_45fbg3rnmk&amp; presentation about xhprof]<br /> * http://techportal.ibuildings.com/2009/12/01/profiling-with-xhprof/<br /> <br /> {{CategoryDeveloper}}</div>

Harryf