gplx/mediawiki/maintenance/benchmarks
Sascha c0fb067595 feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
..
data feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
README.md feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkCommentFormatter.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkEval.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkHooks.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkJsValidate.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkJsonCodec.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkLruHash.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkParse.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkPurge.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkSanitizer.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkSettings.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkTidy.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkTitleValue.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00
benchmarkTruncate.php feat: Mediawiki added, extensions added 2026-06-01 16:02:23 +02:00

README.md

This directory hold several benchmarking scripts used track performances of MediaWiki and/or PHP.

Consistency

To gain greater precision than the time elapsed as reported by the benchmark itself, one can use the perf_events tool on Linux to count the number of CPU instructions, in addition to measuring how long it took to execute them.

This should accurately tell you how much machine code is executed. Note that this does not correctly model the cost of each instruction (especially memory access).

For example:

$ perf stat -e instructions php -d opcache.enable_cli=1 \
  maintenance/benchmarks/benchmarkEval.php --code="Html::openElement( 'a', [ 'class' => 'foo' ] )" \
  --inner=1000 --count=10000

eval:
   count: 10000
    rate:    590.1/s
   total: 16946.61ms
    mean:     1.69ms
      ...

Performance counter stats for 'php maintenance/benchmarks/..':
    83651088078  instructions
   17.225255198  seconds time elapsed
            ...

Fixtures