Performance team meeting summary 26 July 2022

@adamsilverstein: Main WebP work has been merged to core! Ticket is still open because there are several small follow-up patches we’re working on
@mukesh27: Working on
- Core patch follow-up: WebP compatibility: add fallback for non-supporting browsers to cor and Add the new source data
  
  Sponsored
  
  to the media REST API endpoint – PR #3025
- Add the original image’s extension to the WebP file name to ensure it is unique – PR #444
- Enhance JS replacement mechanism for WebP to JPEG to more reliably replace full file name – PR #443
@mehulkaklotar: Working on core patch for support of multiple mime types on image edit/restore flows. PR link
@paulbearne: Seeing some pushback on dominant color proposal; comments would help
@joegrainger: Module proposal: Regenerate existing images
- @joegrainer: Looking to create a new Settings screen to allow administrators to regenerate images to help with performance. Also creating background infrastructure to handle long-running tasks which will be used by the regenerate images job. This will allow users to regenerate images to the correct sizes when changing a theme and to create WebP versions of older images too.
- @pbearne: Hoping that the background processing infrastructure is open for calling by other plugins, a bit like scheduling a cron task
- @joegrainger: That’s the plan; the background processing infrastructure is decoupled from the regeneration of images, so it can be used by other plugins for running their own background jobs
- @zero4281: Love the idea of being able to regenerate images at the click of a button. Has anyone given thought to updating Gutenberg once the picture tag, image srcset, and image regeneration is complete? In theory it should be possible to remove the need for the user to select an image size and just include all image sizes in the srcset and let the web browser choose the size.
  - @flixos90: Great points; updating Gutenberg editor content would be a potential use case for the background process. With image size selection, there’s still value depending on how you place the image.
  - @zero4281: Doesn’t Gutenberg define the width and height in the image tag?
  - @flixos90: If the user resizes it, but by default, it takes dimensions from the image size selected
- @furi3r: Wouldn’t Action Scheduler do the trick?
  - @joegrainger: Took a lot of inspiration from this plugin and made some changes, but background processing infrastructure will work similar to this
- Received 7 thumbs up votes to proceed with this module, so we’ll get started
- @flixos90: Make sure to develop this in a feature branch as it will be quite large
- @spacedmonkey: Might also be useful for dominant color as well, to backfill old images

Feedback requested

See above
Needs Discussion (8 issues)
Needs Dev (1 issue)
Needs Review (1 issue)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey out through 5 September
@tillkruess: Merged https://github.com/WordPress/wordpress-develop/pull/2969 and need core dev approval for https://github.com/WordPress/wordpress-develop/pull/2967. @olliejones proposed some new object caching documentation which is in review.

Feedback requested

See list above
Needs Discussion (3 issues)
Needs Review (2 issues)

Site Health

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
@furi3r: Working on Site Health Trac ticket feedback; not much, so hopefully will be able to merge soon
@shetheliving: Will discuss new module proposal issue from @olliejones for Database Performance Health checks #455 next week