4 * To use a profiler, copy this file to StartProfiler.php,
6 * $wgProfiler['class'] = 'ProfilerStandard';
8 * $wgProfiler['class'] = 'ProfilerXhprof';
11 * $wgProfiler['output'] = array( 'text' );
12 * 'text' can be one (or more) of 'text' 'udp' or 'db'
13 * 'db' requires creating the profiling table, see patch-profiling.sql
15 * The 'text' output will be added to the output page in a comment approriate
16 * to the output's mime type. For a text/html page, this display can be
17 * changed to a preformatted text block by setting the 'visible' configuration
19 * $wgProfiler['visible'] = true;
21 * The 'db' output expects a database table that can be created by applying
22 * maintenance/archives/patch-profiling.sql to your database.
24 * For a rudimentary sampling profiler:
25 * $wgProfiler['class'] = 'ProfilerStandard';
26 * $wgProfiler['output'] = array( 'db' );
27 * $wgProfiler['sampling'] = 50; // one every 50 requests
28 * This will use ProfilerStub for non-sampled cases.
30 * For performance, the profiler is always disabled for CLI scripts
31 * as they could be long running and the data would accumulate. Use
32 * the --profiler parameter of maintenance scripts to override this.