[wp-trac] [WordPress Trac] #57687: Add automated performance testing CI workflow MVP

[WordPress Trac]

#57687: Add automated performance testing CI workflow MVP
--------------------------------------+--------------------------
 Reporter:  adamsilverstein           |       Owner:  mukesh27
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.2
Component:  Build/Test Tools          |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by flixos90):

 @joemcgill Agreed. I think we should for now go with not updating our base
 tag even as new WordPress versions get released. Gutenberg has to do it
 because it has a dependency on WordPress and the newest Gutenberg `trunk`
 can't be used with too old versions of WordPress `trunk`. That's not a
 limitation for core itself though, so I think here we should aim to stick
 with the consistent base tag as long as it's reasonable. As noted, any
 time the base tag would change, metrics recorded before or after are not
 statistically comparable anymore, which means for Gutenberg that the tool
 is only useful for comparing performance within one WordPress release
 cycle.

 As you already mentioned, there will be a few follow up ideas to explore.
 I mentioned some in https://github.com/WordPress/wordpress-
 develop/pull/4139#pullrequestreview-1324456566, IMO the highest priority
 follow up would be to expand the metrics recorded to also include a
 client-side metric (I would suggest to add load time Web Vitals like LCP,
 FCP, and TTFB). But all of those are reasonable iterations, this PR is a
 solid starting point and I think good to commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57687#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform