Manual:$wgProfiler/fr

Détails
Ce paramètre est utilisé pour configurer le profilage de votre installation MediaWiki.

Pour les clés disponibles, voir. Elles incluent :


 * : 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:


 * ProfilerOutputDb expects a database table that can be created by applying  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, 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.

Pour des raisons de performance, le profileur est toujours désactivé pour les scripts CLI parce qu'ils peuvent prendre du temps pour s'exécuter et que les données peuvent s'accumuler. Utilisez le paramètre '--profiler' des scripts de maintenance pour réécraser ceci.

Exemple
Pour un profileur de débogue élémentaire :