The MediaWiki platform team recently found some performance problems with Vector/skins (T351831 and T351807). We would like to setup some tests to monitor and prevent these occurring again. We should talk to the MediaWiki platform team about ideas and come up with a concrete proposal for monitoring/benchmarking our code. We should look at the MediaWiki platform teams intake process and ask them for consultancy support.

Feature summary

In vector and minerva skins we want to devise a test that benchmarks the total load of the full render cycle.

• The test will rely on the length of the call trace, and maybe the sequence of it
  • We can't rely on time, because of the difference in machines and capabilities.
• We could devise a different or additional metrics to consider within the test, the criteria of any metric is that it should be stable and reproducible and comparable. ie: number of loops/iterations
• The test should able to identify regressions of performance based on the chosen metrics.

this is a placeholder task for now to maintain the requirements and the topic. We should expand and detail more later after some experiments.