Manual:$wgProfiler

Details
This setting is used to configure man>Special:MyLanguage/Manual:Profiling|profiling of your MediaWiki installation.

See the StartProfiler.sample file, located in the root of your MediaWiki installation, for more information.

For the available keys see .

They include:


 * : E.g. ProfilerXhprof provides an Xhprof-backed profiler.
 * : Define one or multiple output methods. For multiple output methods at the same time, use an array of class names, one for each output type you want the profiler to generate. For example use the "ProfilerOutputText" profiler. The output classes available to you by default are ProfilerOutputDb, ProfilerOutputDump, ProfilerOutputStats, ProfilerOutputText, and ProfilerOutputUdp.


 * ProfilerOutputStats outputs profiling data as StatsD metrics. It expects that you have set the $wgStatsdServer configuration variable to the host (or host:port) of your statsd server.
 * ProfilerOutputText will output profiling data in the page body as a comment. You can make the profiling data in HTML render as part of the page content by setting the 'visible' configuration flag: $wgProfiler['visible'] = true;
 * ProfilerOutputDb expects a database table that can be created by applying maintenance/archives/patch-profiling.sql to your database.
 * ProfilerOutputDump expects a $wgProfiler['outputDir'] telling it where to write dump files. The files produced are compatible with the XHProf gui.
 * : true or false. If true, output is displayed in HTML rendering (and not only in a comment).
 * : Positive integer. Profile every nth request.
 * : Hostname of the UDP server which receives ????????????????? what ?????
 * Supersedes.
 * : Hostname of the UDP server which receives ????????????????? what ?????
 * Supersedes.
 * Supersedes.


 * : Port of the UDP server which receives ????????????????? what ?????
 * Supersedes.


 * : Format string to use for ????????????????? what ?????
 * Supersedes.


 * : Should the application server hostname be stored in the profiling table?
 * Supersedes.

For performance, the profiler is always disabled for CLI scripts as they could be long running and the data would accumulate. Use the '--profiler' parameter of maintenance scripts to override this.

Example
For a rudimentary sampling profiler:

$wgProfiler['class'] = 'ProfilerXhprof'; $wgProfiler['output'] = array( 'ProfilerOutputDb' ); $wgProfiler['sampling'] = 50; // one every 50 requests

This will use ProfilerStub for non-sampled cases.