Performance Chat Summary: 19 December 2023

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


Priority Projects

Server Response Time

Link to roadmap projects and link to the GitHub project board

Contributors: @joemcgill @swissspidy @thekt12 @mukesh27 @pereirinha

Database Optimization

Link to roadmap projects and link to the GitHub project board

Contributors: @mukesh27 @thekt12

  • No updates this week

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. & CSSCSS Cascading Style Sheets.

Link to roadmap project and link to the GitHub project board

Contributors: @mukesh27 @flixos90 @westonruter

  • @flixos90 No real update, just that I’m currently experimenting with the Interactivity APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., specifically to use it in classic default themes to replace more manual custom JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.. Partly to familiarize myself with the API, partly for a first prototype of something we could potentially do in the future. Should have a first draft PR up for later today. Really for reference more than anything


Link to roadmap projects and link to the GitHub project board

Contributors: @flixos90 @adamsilverstein @joemcgill @pereirinha @westonruter

  • @joemcgill Last week I put together a small experiment to see how the new auto-sizes for lazy-loaded images feature is working now that it’s being implemented in browsers. Based on that exploration, I put together an initial module implementation that can already be used for testing. I plan to update the PR this week.
    • Related – I also opened a new issue to discuss how we want to handle new modules once the unbundling project is complete. Feedback would be appreciated.


Link to roadmap projects and link to the GitHub project board

Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90

  • No updates this week

Ecosystem Tools

Link to roadmap projects and link to the GitHub repo for PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party Checker

Contributors: @mukesh27 @swissspidy

  • @mukesh27 For the Plugin Check, I have been addressing issue 342 and have opened PR 347, which is now ready for review and I also supported in code review process. Moreover, there is positive news that some community contributors are actively working on several issues and have raised corresponding PRs for them. 

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27

Open Floor

  • @desrosj I noticed that the performance tests started failing in some older branches while working on some E2E test related changes. Well, it only seems to be happening for the 6.4 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". currently. But I’m wondering if the needed conditions just haven’t been met for the other branches.
    • @joemcgill I’m only seeing the latest commit fail according to this list. Am I looking at the wrong thing?
    • @desrosj That’s accurate. I was confusing the additional E2E failures with something (potentially) unrelated that I’ve fixed separately. #60095 is what I was working on. The step that is failing seems to be checking 6.1.1 for a baseline if I’m reading it correctly.
    • @joemcgill I’m going to try rerunning that one, since the same commit to the 6.3 branch worked fine.
    • @desrosj
    • FWIW, I committed the fix for 60095 in the 6.1 branch this morning, and this workflow was from yesterday. Maybe the re-run does not include changes for the other branch because they were not there when this change was made? Started a manual run for 6.4 to try and rule that out.

Our next chat will be held on Tuesday, January 2, 2024 at 16:00 UTC in the #core-performance channel in Slack.

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