Meeting agenda here and the full chat log is available beginning here on Slack.
Mini bug scrub of performance issues for 6.1.1
- See here
- https://core.trac.wordpress.org/ticket/56923 – PR committed; should become available when @mamaduka syncs Gutenberg to core on Thursday
- https://core.trac.wordpress.org/ticket/56815 – assigned to @flixos90 for review
- https://core.trac.wordpress.org/ticket/56900 – assigned to @peterwilsoncc for commit
- https://core.trac.wordpress.org/ticket/56945 – @flixos90 has PR in progress at https://github.com/WordPress/wordpress-develop/pull/3536 that needs review and feedback, especially from Gutenberg team. @annezazu working to loop someone in there.
- https://core.trac.wordpress.org/ticket/56948 – ready for commit, just needs a final review; assigned to @peterwilsoncc
- https://core.trac.wordpress.org/ticket/56952 – @adamsilverstein to look into
- https://core.trac.wordpress.org/ticket/56974 – @flixos90 took a first look at the PR last week and will give it a comprehensive review today
- https://core.trac.wordpress.org/ticket/56990 – @adamsilverstein‘s changes need review/testing
- https://core.trac.wordpress.org/ticket/56991 – @spacedmonkey‘s fix at https://github.com/WordPress/wordpress-develop/pull/3575 needs review
- https://core.trac.wordpress.org/ticket/57012 – ready for commit by @peterwilsoncc
Focus area updates
Images
@adamsilverstein @mikeschroder
GitHub project
- @adamsilverstein: Discovered a library, jSquash, that brings image format encoding/decoding to the web. Tested a bit and oping to use it to enhance the core image block with modern image capabilities. If successful, would let us introduce AVIF support without depending on server-side support.
- @mehulkaklotar: Working on #563 for Performance Lab to change default WebP quality to 82; PR needs review.
Feedback requested
Object Cache
@tillkruess @spacedmonkey
GitHub project
- @spacedmonkey: Working mostly on 6.1.1 issues, but a few for 6.2, as well:
- https://github.com/WordPress/wordpress-develop/pull/3544
- https://github.com/WordPress/wordpress-develop/pull/3528
- https://github.com/WordPress/wordpress-develop/pull/3534
- https://github.com/WordPress/wordpress-develop/pull/3366
- https://github.com/WordPress/wordpress-develop/pull/3365
- https://github.com/WordPress/wordpress-develop/pull/3178
- @tillkruess: Chatted with @johnjamesjacoby about adding a health check for the new
wp_cache_supports() function to show which object caching features are supported/not supported but recommended. See https://github.com/WordPress/wordpress-develop/pull/3347. For example, get_multiple() is quite important. Any feedback on adding as a health check? - @spacedmonkey: Now have
wp_cache_supports in core that we could use and wp_cache_supports( 'get_multiple') in all options. Instead of loading all options in one cache key, load each in their own cache key and all in single call. -
Feedback requested
Measurement
N/A
GitHub project
Feedback requested
JS & CSS
@aristath @sergiomdgomes
GitHub project
Feedback requested
Database
@olliejones
GitHub project
Feedback requested
Infrastructure
@flixos90
GitHub project
- @flixos90: Plugin codebase is now updated to reflect our recent modifications to the focus areas per https://github.com/WordPress/performance/pull/566, thanks to @mukesh27
Feedback requested
Our next chat will be held on Tuesday, November 15, 2022 at 16:00 UTC in the #core-performance channel in Slack.
#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community
#meta