Performance team meeting summary 24 May 2022

Table of Contents

Announcements

Reminder: No meeting next week, 31 May, as many folks will be traveling/prepping to travel to WCEU
We’ll be well-represented at WCEU with three talks and a large section of the WP community booth; see this doc for details and info on contributing
Bethany will be offline 1-15 June and @clarkeemily will run the 6 and 13 June meetings

@adamsilverstein: Finishing up some WebP issues, primarily around handling edit and restore actions correctly. Several multi-mime type/WebP features in the plugin were not in the core patch yet, so working on follow-up core patches to add them. For example, this patch adds the ability to always use the smaller image size for image references. Also did some research this week on a polyfill to enable WebP support for older browsers and developed a script to use a capability check before dynamically loading the library to add support. We also have sent out a survey to hosting providers about image storage to get more data about the impact of WebP on storage.
@pbearne @spacedmonkey: Add low quality image placeholders #19 should be ready to merge (example)
- @adamsilverstein will take another look and @shetheliving will make sure @flixos90 does when he’s back online
- @adamsilverstein: Since this is a proposed core patch, is there already a matching Trac ticket?
- @pbearne @spacedmonkey: No; that is a wider conversation about porting over functionality to core and when/how this should happen (and how/if we remove it from the plugin)
- @shetheliving: We’ll add this to the 6 June meeting agenda cc @clarkeemily

@spacedmonkey: Working on Prime users in cache in WP_Query #2722 and Use metadata api in *_network_options #2478 in hopes of getting them in 6.1. Also hopes to work on Cache the results of the posts_request_ids query #22176, which would be a massive win and the biggest thing we’ve done in this project to date. Now that more and more of the page is stored in Posts with Full Site Editing, ensuring that caching/no duplicate queries are in WP_Query is necessary.
- @adamsilverstein: Great to see these older tickets getting some traction, as they’ve been known improvements for a long time
- @spacedmonkey: Created a new patch for that that needs work, but is working if anyone wants to take a look

N/A

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
@furi3r: Add Site Health test for full page caching (advanced cache) #220 was moved to 1.2.0 is just about ready and waiting for testing. Need to determine how/if we want to port any existing Site Health modules to core.
- @shetheliving: @akshitsethi is working on a Trac ticket for merging the WebP support SH check into core along with the WebP on new image uploads work
- @furi3r: Create Autoloaded Options Core Documentation #234 needs to be completed to remove the Experimental label on this SH check in the plugin and eventually merge into core; @shetheliving to follow up

N/A

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

@flixos90 offline
@shetheliving: If you haven’t already, review the module proposal workflow and leave any feedback on the PR. Next step would be to merge this and create a new GH issue template for module proposals.
@shetheliving: Reminder that next release will be 1.2.0 on Monday, June 20, so we should target merge for anything for that release by about June 15.

@spacedmonkey: Is there anything we want to specifically focus on for 6.1?
- @olliejones: Maybe more/better large-site performance increases? WHERE wp_usermeta.meta_key = 'wp_capabilities' AND meta_value LIKE '%editor%' is the performance botch; ticket here. Probably needs another because this one mentions Gutenberg, but problem also exists in Users, Posts, and Pages.
- @clorith: Query improvements for 6.0 were nice and don’t look large, but it all adds up quickly, so would love to see more of a review of queries and how they can be improved. May be some old ones from years back where smarter queries now exist.
- @spacedmonkey: Would focus on SQL_CALC_FOUND_ROWS is deprecated as of MySQL 8.0.17 #47280
- @pbearne: Have been digging into the rest and FSE queries are seeing a lot of low-hanging fruit that could be improved