Performance Chat Summary: 26 September 2023
Meeting agenda here and the full chat log is available beginning here on Slack.
Announcements
- Welcome to our new members of #core-performance
- WordPress 6.4 beta 1 is
September 26, 2023today - Early version of WordPress plugin checker launched
Priority Projects
class=”wp-block-heading” id=”images”>Server Response Time
Contributors: @joemcgill @spacedmonkey @aristath @swissspidy @thekt12 @mukesh27
- @spacedmonkey committed [56621], [56650], [56677], [56678], and [56683]
- @thekt12 is working on #59314
- @flixos90 committed [56681] and just opened a follow up bug fix PR that would be great to commit in the next hour if there is consensus (since committed in [56717])
- @mukesh27 has been working on additional unit tests for #22192
- @joemcgill posted some additional benchmarking for the two approaches in flight for #57789, and plans to do some more profiles to get more detailed info on both. He is still planning on tracking these PRs in the Gutenberg repos but have punted to 6.5 for now to keep the release moving while this is getting worked out.
Database Optimization
Contributors: @spacedmonkey @mukesh27
- @spacedmonkey committed [56656] and is currently reviewing a PR for #59442 which @thekt12 has been working on
- @pbearne would like to start working/focus on the option auto-loading issue. now that there is the new filter to allow easy shortcutting from [55256]
- @flixos90: There are a few more existing ideas around, some of which are being worked on already, such as #42441
- For any new ideas, a good next step would be to open issues. Depending on what you envision, you may either want to open a new Trac ticket or a new module proposal in the Performance Lab plugin
- There’s also the autoloaded options Site Health check in Performance Lab, for which there are a few ideas to make it more helpful
JavaScript & CSS
Contributors: @mukesh27 @10upsimon @westonruter @spacedmonkey
- @westonruter committed elimination of manual construction of script tags in
WP_Scriptsand of inline scripts on frontend/login screen in [56687] (see #58664). With this, Strict CSP can now be opted into on the frontend and wp-login screen. Followed up on prior ticket which sought to do the same for all of WP, and opened new ticket to complete effort in admin. - @westonruter also iterated on PR for #55491. In a bug scrub yesterday, we agreed this ticket is actually a defect and not an enhancement, so it can still land after beta1 today
Images
Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill @pereirinha
- @flixos90 committed [56651], [56690], and [56693]
- @pereirinha could use some help to track the tickets that need help
- @flixos90: One of the most flexible ways to search Trac with various filters is the https://core.trac.wordpress.org/query URL
- For example, this query shows all remaining 6.4 tickets with a
performancefocus; it looks like most tickets there are already assigned but please feel free to take a closer look and familiarize yourself with those issues to see if you’re interested in a particular ticket and/or have additional feedback
Measurement
Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90
- @flixos90 re-shared the post from last week here in case you missed it prior: https://make.wordpress.org/core/2023/09/19/analyzing-the-core-web-vitals-performance-impact-of-wordpress-6-3-in-the-field/
- @joemcgill will get some new tickets added for the improvements we want to make to the summaries in the CI performance workflows
Ecosystem Tools
Contributors: @mukesh27 @swissspidy @westonruter
- @mukesh27 is working on issue https://github.com/10up/plugin-check/issues/253 for Plugin Checker.
Creating Standalone Plugins
Contributors: @flixos90 @mukesh27 @10upsimon
- @10upsimon pretty much finalized https://github.com/WordPress/performance/issues/651, has implemented necessary logic for redirection back to WPP Settings Screen following certain standalone plug-in actions, will outline in code review given that a few approaches needed to be tested before arriving at the working solution.
- @flixos90 is looking forward to taking a closer look
Open Floor
- @spacedmonkey raised #42441
- The PR needs review and feedback
- There was consensus that due to a lack of feedback this should be punted to the 6.5 milestone
- Let’s continue discussing on the ticket so we can figure out a good approach for 6.5
- @thekt12 has updated the PR for #59442 and would like additional feedback since he is not confident if this leads to any new issue as the new approach does change how cache key is generated for query
Our next chat will be held on Tuesday, October 3, 2023 at 15:00 UTC in the #core-performance channel in Slack.
