Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

• Reminder: Performance team roadmap for 2023 https://github.com/WordPress/performance/issues/631 If you’re actively contributing to the WordPress Performance Team or plan to do so this year, please share your priorities for 2023 as a comment on this issue before end of day Wednesday February 15, 2023
• Team rep nomination reminder, please add your nominations for Performance Team Rep by Friday, February 24 2023

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

• @adamsilverstein no new updates this week
• @mukesh27 working on Check for existing $metadata[‘sizes’] to reduce PHP warnings and will submit PR soon.

Feedback requested

• See above
• Needs Discussion (10 issues)
• Needs Dev (2 issues)

Object Cache

@tillkruess @spacedmonkey

GitHub project

• @spacedmonkey I would love eyes on https://core.trac.wordpress.org/ticket/12821

Feedback requested

• See above
• Needs Discussion (4 issues)
• Needs Review (1 issue)

Measurement

N/A

GitHub project

• @joegrainger making good progress on the Plugin Checker. We’re starting to finalise the infrastructure and should have a working plugin running some initial checks by end of the month. You can track progress on the GitHub repo and leave any thoughts/ideas you may have. The repo will be moved to the WordPress organisation when ready
• @mukesh27 I would like to share an update for Automated Performance Testing that @adamsilverstein already share blog post on WordPress core.
  • Issues that completed and merged in feature/automated-performance-testing-mvp branch.
    • Set up initial GitHub action for performance tests – PR #6
    • Create a mini-MU plugin for the Server-Timing API – PR #7
  • AC ready for review.
    • Record Server-Timing metrics during GH workflows
    • Log server metrics to the codehealth dashboard
  • We will open a PR against the WordPress trunk once the initial version is complete. Feel free to take a look at the issues and leave any thoughts or ideas you may have.
• @joemcgill Additionally, I’ve been starting to work on an experimental implementation of XHProf with wp-env to help make it easier for folks to do general performance profiling tasks. See: https://github.com/joemcgill/gutenberg/pull/1 as a starting point.
• @10upsimon updates on Enhancing the Scripts API with a loading strategy
  • Documentation approved, although there was a comment added post approval that I have addressed. It does not change the work, but it does result in the need to confirm that the blocking strategy is not to be confused with the blocking  script attribute itself.
  • GitHub issues have been finalized and broken down into 4x milestones in a separate sheet, estimates are present for all issues in the sheet, although not all issues are in GH yet.
  • GH Issues and AC’s have been added to the project board for Milestones 1, 2 and 3 and have been assigned to @joemcgill for review. It looks like all except for one have been approved (at the time of writing) as they’ve been moved to the backlog
  • I’m in the process of breaking down issues for Milestone 4
  • Trac ticket to be posted by Friday, I see no risks thereto.
  • Engineering will commence next week on Milestones 1, 2 and 3

Feedback requested

• Needs Discussion (5 issues)
• Needs Review (1 issue)

JS & CSS

@aristath @sergiomdgomes

GitHub project

• No updates

Feedback requested

• Needs Discussion (4 issues)
• Needs Review (2 issues)

Database

@olliejones

GitHub project

• @olliejones I’ve been hammering on the low end persistent object cache, looks good.
• @aristath These past couple of weeks I continued working on the SQLite database implementation. There’s a lot of work to do, but things are looking good. Started collaborating with @zieladam as well in an effort to improve some things and make the implementation more stable.

Feedback requested

• Needs Discussion (3 issues)
• Needs Review (2 issues)

Infrastructure

@flixos90

GitHub project

• @flixos90 2 small fixes related to infrastructure code landed this week, as well as the WP version bump to 6.1 and removal of the obsolete modules: https://github.com/WordPress/performance/pulls?q=is%3Apr+label%3AInfrastructure+milestone%3A2.0.0+is%3Aclosed
• @flixos90 Reminder that the PL 2.0.0 release is going to be on February 20 (as usual, the 3rd Monday of the month)
• @flixos90 There are still 2 PRs in the milestone that haven’t seen any updates in a while: https://github.com/WordPress/performance/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.0.0 Friendly ping @aristath and @adamsilverstein to please follow up if we want to get them into the 2.0.0 release
• @flixos90 update on Unbundling the Performance Lab plugin
  • I summarized last week’s conversation outcome in https://github.com/WordPress/performance/issues/618#issuecomment-1410903536. There have been a few replies afterwards, still a few things remain to finalize on how to break out the modules; please review and respond with your feedback on the issue
  • Separately, there are already a few engineering efforts which we can start, regardless of the exact outcome in the above discussions. I opened a number of issues and started to add proposed requirements:
    • Likely the first piece would be https://github.com/WordPress/performance/issues/635
    • Followed by https://github.com/WordPress/performance/issues/636 and https://github.com/WordPress/performance/issues/639
  • Please take a look, it would be great to get more feedback on the engineering approach for unbundling
  • We can keep discussing the approach on the issues, but preferably we should begin working on code for at least the first issue next week, to not have this stagnate
  • You can always get an overview of all unbundling related issues through a new label: https://github.com/WordPress/performance/labels/Creating%20standalone%20plugins

Feedback requested

• Needs Discussion (7 issues)
• Needs Review (2 issues)

Open Floor

• @flixos90 Just sharing here that I discovered (probably?) a major performance regression in 6.2 for classic themes: https://core.trac.wordpress.org/ticket/57648
  • I’m going to follow up on that ticket shortly to collaborate with @oandregal as he is seeing slightly different results. Of course there is a chance that something specifically in my analysis went wrong, but we will have to validate that data

Our next chat will be held on Tuesday, February 14, 2023 at 16:00 UTC in the #core-performance channel in Slack.

#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community

#core-performance, #meta