Performance Chat Summary: 3 January 2023


Meeting agenda here and the full chat log is available beginning here on Slack.
Announcements
- @mxbclang: Next week’s chat will be dedicated to discussing next steps on Matt’s request to split out features from Performance Lab (see blog post comment and Slack)
- @olliejones has proposed some ideas and @flixos90 and @tweetythierry have also been considering options
Focus area updates
Images
@adamsilverstein @mikeschroder
- @pbearne: Dominant color in Media Library code is ready for review: https://github.com/WordPress/performance/pull/587
Feedback requested
- See above
- Needs Discussion (10 issues)
- Needs Dev (1 issue)
Object Cache
- @spacedmonkey: Focusing on:
- @spacedmonkey: Would really like eyes on https://github.com/WordPress/wordpress-develop/pull/3793, this was a bug introduced in 6.1 with
WP_Query
caching and want to get merged for 6.1.2 - @spacedmonkey: Created a few issues for bugs/improvements that would be good first bugs:
Feedback requested
- See above
- Needs Discussion (4 issues)
- Needs Review (1 issue)
Measurement
N/A
- @joegrainger: Plugin Checker work in progress and coming along nicely
Feedback requested
- Needs Discussion (5 issues)
- Needs Review (1 issue)
- Needs Testing (1 issue)
JS & CSS
- No updates
Feedback requested
- Tree-shaking block styles on the frontend #41020
- Needs Discussion (4 issues)
- Needs Review (2 issues)
Database
- No updates
Feedback requested
- Needs Discussion (3 issues)
- Needs Review (3 issues)
Infrastructure
- @flixos90: Matt’s request will be a major Infrastructure topic. Will leave some thoughts on https://github.com/WordPress/performance/issues/618 so we can begin to discuss, but a real discussion should occur in next week’s chat since it’s more synchronous. See also @tweetythierry‘s reply to Matt here which mentions some potential options for us to think about.
- @olliejones: Is there any prospect of getting core to add a new drop-in slot to avoid overloading
object-cache.php
with the monitoring stuff?- @flixos90: Adding a new slot will be challenging; defining the scope and whether it’s justified will likely take quite a while. That said, worth exploring in a Trac ticket, but should probably come up with a solid proposal first.
- @manuilov: If we need to split the plugin, seems like the most appropriate option is the second approach suggested by Thierry. Will need to extract modules as individual plugins and keep PL as a wrapper focused on central infrastructure and recommending individual plugins. Otherwise, if we deprecate PL, people will be less able to find new modules/plugins.
- @olliejones: Is there any prospect of getting core to add a new drop-in slot to avoid overloading
Feedback requested
- Needs Discussion (6 issues)
- Needs Review (3 issues)
Open floor
- @olliejones: Is there a load-testing/performance benchmarking setup? Maybe a sample big site with a bunch of jmeter scripts or something similar?
Our next chat will be held on Tuesday, January 10, 2023 at 16:00 UTC in the #core-performance channel in Slack.
#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community