<div style="text-align:center"></div><div>
<p><a href="https://make.wordpress.org/core/2023/03/07/performance-chat-agenda-07-march-2023/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1678204771942099">beginning here on Slack</a>.</p>
<h2 class="wp-block-heading">Announcements</h2>
<ul>
<li>Proposed update to our chat structure for future weeks to be focused more around our <a href="https://make.wordpress.org/performance/roadmap-2023/">2023 performance roadmap</a>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Focusing on the roadmap items sounds great to me. I’d say some of those points are rather broad though, maybe we can still go a bit more granular per project. There’s also some projects on the roadmap that are well underway while others are merely ideas that may not see a lot of updates soon, so we need to think about how to balance that
<ul>
<li><a href="https://profiles.wordpress.org/clarkeemily/" class="mention"><span class="mentions-prefix">@</span>clarkeemily</a> I think that would be the plan, to dive more into those sub-bullet point per priority as listed in our roadmap (sorry, should have clarified that!)</li>
</ul>
</li>
<li><strong>This was agreed</strong> – for future meetings, the agenda will be structured below, with the goal of diving deeper into each roadmap priority sub-project
<ul>
<li>Announcements</li>
<li>Roadmap priorities:
<ul>
<li>Server response time</li>
<li>Database optimization</li>
<li>JavaScript &#038; CSS</li>
<li>Images</li>
<li>Measurement</li>
<li>Ecosystem tools</li>
</ul>
</li>
<li>Infrastructure</li>
<li>Open floor</li>
</ul>
</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="focus-group-updates">Focus area updates</h2>
<h3 class="wp-block-heading" id="images">Images</h3>
<p><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/mikeschroder/" class="mention"><span class="mentions-prefix">@</span>mikeschroder</a></p>
<p><a href="https://github.com/WordPress/performance/projects/1">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> not around today so no updates</li>
</ul>
<h4 class="wp-block-heading" id="feedback-requested">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22">Needs Discussion</a> (11 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Dev%22+">Needs Dev</a> (1 issue)</li>
</ul>
<h3 class="wp-block-heading" id="object-caching">Object Cache</h3>
<p><a href="https://profiles.wordpress.org/tillkruess/" class="mention"><span class="mentions-prefix">@</span>tillkruess</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a></p>
<p><a href="https://github.com/WordPress/performance/projects/6">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> I have been doing some discovery around lazy loading all meta data in WordPress
<ul>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57645" target="_blank">https://core.trac.wordpress.org/ticket/57645</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57801" target="_blank">https://core.trac.wordpress.org/ticket/57801</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57496" target="_blank">https://core.trac.wordpress.org/ticket/57496</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Lazy loading term and comment is super easy, as this is done elsewhere in core. Post, user and site might be a little harder
<ul>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57625" target="_blank">https://core.trac.wordpress.org/ticket/57625</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57802" target="_blank">https://core.trac.wordpress.org/ticket/57802</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57593" target="_blank">https://core.trac.wordpress.org/ticket/57593</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Otherwise, created a couple of PRs related to server speed that could use some eyes
<ul>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57864" target="_blank">https://core.trac.wordpress.org/ticket/57864</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57705" target="_blank">https://core.trac.wordpress.org/ticket/57705</a></li>
</ul>
</li>
</ul>
<h4 class="wp-block-heading" id="feedback-requested-2">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+">Needs Discussion</a> (5 issues)</li>
</ul>
<h3 class="wp-block-heading" id="measurement">Measurement</h3>
<p>N/A</p>
<p><a href="https://github.com/WordPress/performance/projects/5">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a> We are working towards completing the infrastructure for the Plugin Checker and once done we’ll have a working plugin with some initial checks. At that point we’ll be taking the time to do some initial testing, review the infrastructure and make any changes before working on the additional checks. You can see progress on the <a rel="noreferrer noopener" href="https://github.com/10up/plugin-check/" target="_blank">GitHub repo</a> here. Feel free to leave any thoughts/ideas you may have in the repo too!</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> Automated performance testing has been committed to the WP core repo https://core.trac.wordpress.org/changeset/55459
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> The first run of the new performance workflow ran perfectly, except for successfully posting results to the codevitals.run dashboard. I assume it’s because we either have an incorrect project token or some other change was made to the API there. I’ll follow up with <a href="https://profiles.wordpress.org/youknowriad/" class="mention"><span class="mentions-prefix">@</span>youknowriad</a> to get this working when he’s back around. Regardless, this is pretty cool to see (copied over from Mar 3)</li>
</ul>
</li>
</ul>
<h4 class="wp-block-heading" id="feedback-requested-1">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+">Needs Discussion</a> (5 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+">Needs Review</a> (1 issue)</li>
</ul>
<h3 class="wp-block-heading" id="javascript">JS &#038; CSS</h3>
<p><a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> <a href="https://profiles.wordpress.org/sergiomdgomes/" class="mention"><span class="mentions-prefix">@</span>sergiomdgomes</a></p>
<p><a href="https://github.com/WordPress/performance/projects/3">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> update on <strong>WRT Script Loading Strategy</strong>:
<ul>
<li><a target="_blank" href="https://core.trac.wordpress.org/ticket/12009#comment:83" rel="noreferrer noopener">Trac Ticket 12009</a> has been updated with a comment describing the work being carried out, and brief instructions on where and how to follow progress. We encourage early feedback.</li>
<li>Work on <a target="_blank" href="https://github.com/orgs/10up/projects/14/views/1?filterQuery=milestone%3A%22Milestone+2%22" rel="noreferrer noopener">milestone 2 issues</a> has been completed, and all code approved, unit tested and functionally tested. Further holistic testing is underway but is not a blocker to progress.</li>
<li><a target="_blank" href="https://github.com/orgs/10up/projects/14/views/1?filterQuery=milestone%3A%22Milestone+3%22" rel="noreferrer noopener">Milestone 3 work</a> is underway and tracking well.</li>
<li>We continue Investigating potential interoperability issues to assess how developers most commonly solve for the <code>async</code> and <code>defer</code> script applications in the absence of this enhancement that is underway, so that we can better understand if and how we need to potentially solve for this in the interest of preserving the work we are doing in core, and being mindful of backward compatibility.</li>
</ul>
</li>
</ul>
<h4 class="wp-block-heading" id="feedback-requested-3">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+">Needs Discussion</a> (4 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+">Needs Review</a> (2 issues)</li>
</ul>
<h3 class="wp-block-heading">Database</h3>
<p><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a></p>
<p><a href="https://github.com/WordPress/performance/projects/7">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> Work continues on the SQLite project. Starting to look at popular plugins with their own SQL. (Thousands of them.) Trying to get the top ten to work. (WooCommerce, Yoast, etc).
<ul>
<li>The work is happening in the standalone repo. Migrating to the monorepo is still in the future.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> You can use <a rel="noreferrer noopener" href="https://wpdirectory.net/" target="_blank">https://wpdirectory.net/</a> to find plugins that do custom database queries</li>
</ul>
</li>
</ul>
<h4 class="wp-block-heading" id="feedback-requested-1">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F7">Needs Discussion</a> (3 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+">Needs Review</a> (2 issues)</li>
</ul>
<h2 class="wp-block-heading" id="infrastructure">Infrastructure</h2>
<p><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a></p>
<p><a href="https://github.com/WordPress/performance/projects/2">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> started working on milestone 1 tasks for <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/656" target="_blank">creating a standalone plugin.</a>
<ul>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/performance/pull/662" target="_blank">PR 662</a> for implementing CLI command for a build process to transform modules into standalone plugins is ready for review</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I’ll give the above another review today, really excited to see it moving forward</li>
</ul>
</li>
</ul>
<h4 class="wp-block-heading" id="feedback-requested-1">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+">Needs Discussion</a> (6 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+">Needs Review</a> (3 issues)</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> Is there any intentional liaison between us and <a href="https://wordpress.slack.com/archives/C3D6T7F8Q">#hosting-community</a>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> I know the hosting community is keeping on eye on our work, see <a rel="noreferrer noopener" href="https://wordpress.slack.com/archives/C3D6T7F8Q/p1677695456489839" target="_blank">https://wordpress.slack.com/archives/C3D6T7F8Q/p1677695456489839</a></li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> I meet with some hosting companies at WordCamp Asia, but we could do a better job at building bridges between these teams.
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> Can you persuade your contacts to lurk here, or identify themselves? Would love to know what they wish they had from performance.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> I would really like to have a conversation with a couple of hosting dbms-ops people, to learn more about their problems and how we can help address them.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> there are people like <a href="https://profiles.wordpress.org/desrosj/" class="mention"><span class="mentions-prefix">@</span>desrosj</a> (Bluehost) and <a href="https://profiles.wordpress.org/mikeschroder/" class="mention"><span class="mentions-prefix">@</span>mikeschroder</a> (GoDaddy) that might be able to help</li>
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a> that’s a conversation worth having with agencies too</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Humanmade does a lot of hosting with their platform</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> can make some intros to help <a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/tillkruess/" class="mention"><span class="mentions-prefix">@</span>tillkruess</a> raised a concern over comments on <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/132" target="_blank">https://github.com/WordPress/performance/issues/132</a>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> The TLDR of 132, is that as we support older version of DBs, we can’t rollout the indexes? Can we do a progressive enhancement for newer DBs?</li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> To oversimplify, <code>(191)</code> indexes don’t do what big sites need. “Progressive enhancement” means “two versions of the database definition”. Is there testing capability? <a rel="noreferrer noopener" href="https://www.plumislandmedia.net/index-wp-mysql-for-speed/wordpresss-prefix-keys/" target="_blank">https://www.plumislandmedia.net/index-wp-mysql-for-speed/wordpresss-prefix-keys/</a> is a writeup on the topic.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> There are other examples of progressive enhancements in core. And there is a different schema for the user table for multisite for example. Any thoughts on progressive enhancements like this <a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a></li>
<li><a href="https://profiles.wordpress.org/tillkruess/" class="mention"><span class="mentions-prefix">@</span>tillkruess</a> I’m strongly in favor of databases indices as an opt-in feature.</li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> In schema.php we’d put <code>if (the database uses the barracuda storage engine ) { lots of data definition language }</code></li>
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a> The answer I always give when talking about introducing optional features is, is the intended user capable of making an informed decision about whether or not to enable the feature? If the “user” in this context is a large scale web host then yes, if the “user” is a freelance integrator without much SQL experience then no. So if we can guide an informed decision to be made then I’m in favor of these indices enhancements being opt-in, as much as I’m not a fan of differing schemas the benefit outweighs that here IMO</li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230314T1600"><abbr class="date" title="2023-03-14T16:00:00+00:00">Tuesday, March 14, 2023 at 16:00 UTC</abbr></a> in the <a href="https://wordpress.slack.com/messages/core-performance/">#core-performance channel</a> in <a href="https://make.wordpress.org/chat/">Slack</a>.</strong></p>
<p class="o2-appended-tags"><a href="https://make.wordpress.org/core/tag/core-media/" class="tag"><span class="tag-prefix">#</span>core-media</a>, <a href="https://make.wordpress.org/core/tag/core-performance/" class="tag"><span class="tag-prefix">#</span>core-performance</a>, <a href="https://make.wordpress.org/core/tag/performance/" class="tag"><span class="tag-prefix">#</span>performance</a>, <a href="https://make.wordpress.org/core/tag/performance-chat/" class="tag"><span class="tag-prefix">#</span>performance-chat</a>, <a href="https://make.wordpress.org/core/tag/summary/" class="tag"><span class="tag-prefix">#</span>summary</a></p>
</div>

The WordPress Foundation and WooCommerce have joined Automattic and Matt Mullenweg in countersuing WP Engine,…
The first-ever CloudFest USA Hackathon, taking place November 4 in Miami, will bring together contributors…
Canada’s largest gathering of WordPress enthusiasts drew a strong turnout at Carleton University last weekend,…
WooCommerce 10.3 was released this week, introducing one of the most requested features for store…
Automattic has hired GiveWP co-founder Devin Walker as Artistic Director for Jetpack, where he will…
WordPress 6.9 Beta 1 was released on Tuesday for testing ahead of its planned December…