Performance team meeting summary 27 September 2022

Table of Contents

Announcements

@shetheliving: Mission and philosophies review
- Drafting a Handbook for our site and would like to include overall mission for the team
- Please review and leave comments on the doc with your thoughts

@spacedmonkey: Need dev notes for https://core.trac.wordpress.org/ticket/53232
- @shetheliving: Will work with Adam to see if he can pick this up
@eugenemanuilov: Worked on #524 to disable JPEG subsizes generation for WebP images; #525 also in progress and almost ready for CR
@ankitgade: Working on background processing infrastructure related to image regeneration
- 1. Job class PR is awaiting review: https://github.com/WordPress/performance/pull/507
  2. Background process runner PR is in draft as it has dependency on #507: https://github.com/WordPress/performance/pull/512
  3. Admin queue screen PR is in progress: https://github.com/WordPress/performance/pull/533
@shetheliving: No updates on next steps on WebP just yet; discussions still ongoing

N/A

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
No updates

N/A

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
@robinwpdeveloper: Incorrect message about the status of WP_AUTO_UPDATE_CORE #51041 was committed today

@aristath: No movement on the JS front recently, so focusing on general performance improvements instead, including #56636, #56637, #56654 and just a few minutes ago #56666. The process I’ve been following is to basically run vanilla WP using Xdebug-profiling, examine the results using webgrind and try to reduce the amount of function calls – as well as their cost. Generally small tweaks, with relatively big benefits. Last week #55005 was also merged in Core, so overall I believe WP 6.1 contains a lot of nice and impactful performance changes – as highlighted by all the updates from other folks above.

@shetheliving: Vote about bumping minimum requirement to WP 6.0 open through this Friday; please vote if you haven’t already
@mukesh27: Add JavaScript coding standard workflow #515 and Update @wordpress/env to latest version #546 need review

@spacedmonkey: Think this is a great idea and could be useful in core for running unit tests and for other projects like wordpress-wasm. Wonder if the performance team should help take on this problem, even if it is to review the solution and ensure that there’s no performance regression.
@aristath: Understand that testing could be difficult, so currently converting it to work as a plugin in this repository. Trying to convert to something that would make sense for core and then publish in the .org repo as a featured plugin. Hoping if this is in the form of the plugin, more people will test and provide feedback. Also noting that the initial proposal focused on small-to-medium sites, but there’s great potential for growth in other areas as well where large sites can take advantage of SQLite.
- @spacedmonkey: I’ve forked hyperdb and run very large multisites, can provide context here
- @aristath: We’ll need lots of context once we get rolling – the prospect of pairing SQLite and hyperdb is very exciting