Performance Chat Summary: 20 May 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

• @westonruter shared work on #61734 / PR #8815 adding fetchpriority support for Scripts and Script Modules.
• @spacedmonkey shared a desire to see some eyes on #59592
  • @spacedmonkey says it seems to have a massive effect for those using object caching. The change has unit tests and has been been reviewed by a non committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.. Just needs another committers to give it the thumbs up.
  • @spacedmonkey would like to land this ASAP, to allow as much time as possible to test this change.
  • @rmccue confirmed support for the proposal but cannot review the code in the short term.
  • @westonruter asked whether there’s TTFB benchmarking data available for the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..
    • @spacedmonkey noted there would’t be any noticeable difference there. This change would help high traffic site and helps database and object cache performance.
    • @tillkruess noted It will just reduce memory usage in the cache significantly, or make it easier to keep it low.
• @spacedmonkey noted that #58001, #63021, and #57496 are still awaiting a second round of review.
  • @mukesh27 mentioned @flixos90 already reviewed and shared some feedbacks for #58001 / PR #5098.
  • @swissspidy added that the other PRs have some merge conflicts that could use a refresh.

Open Floor

• @b1ink0 brought up some confusion around the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub timing, asking if the schedule should be revisited to avoid conflicts. (Bug scrub schedule link)
  • @westonruter asked if the time had already been moved to avoid conflicting with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat.
  • @westonruter confirmed that, according to the Make Meetings page, it had not been adjusted.
  • @swissspidy suggested moving the bug scrub to Tuesdays on alternate weeks from office hours.
  • @westonruter and @flixos90 both supported the idea.
  • @swissspidy updated the Make Meetings page and Bug scrub schedule, then shared the schedule for the next meetings as follows:
    • May 27 – bug scrub (potentially led by @adamsilverstein)
    • June 3 – office hours (@swissspidy would probably cancel that one because of WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe)
    • June 10 – bug scrub
    • June 17 – office hours

Our next chat will be held on Tuesday, June 3, 2025 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary