YSlow is Yahoo!'s page performance tool. It runs under PhantomJS (see http://yslow.org/phantomjs/) for easy integration with Jenkins.
There should be a Jenkins job to run YSlow against a page and to -1 the change if the overall score drops relative to an established baseline.
Version: wmf-deployment
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Krinkle | T59137 Add a voting YSlow job to Jenkins | |||
| Open | None | T67394 [EPIC] Performance testing environment |
+1. This should make front-end performance regressions visible before they become an issue in production.
Not sure how we can get a job running reliably / offering same performances. Maybe a dedicated slave that would run only one job at a time.
@ori has been working on various benchmark tools. If he or other teams have a specific need and proposal for jobs that should run after each commit of some git repository (or from a timed-schedular in Jenkins), a task can be filed for that.
However this task seems too vague and is not actionable from Continuous-Integration-Infrastructure perspective. I'd recommend interested parties to come up with a proposal for the environment (e.g. MediaWiki core + skin + certain extensions), and implement the actual build script (e.g. run headless Chromium with YSlow, or some other plugin). We then need to find a way to store past build information by target branch (or limit to master) and have the job run on unmerged patches to compare against.