<div style="text-align:center"></div><div>
<p><a href="https://make.wordpress.org/core/2023/03/28/performance-chat-agenda-28-march-2023/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1680015569916919">beginning here on Slack</a>.</p>
<h2 class="wp-block-heading">Announcements</h2>
<ul>
<li>None today</li>
</ul>
<h2 class="wp-block-heading" id="focus-group-updates">Priority Projects</h2>
<h3 class="wp-block-heading" id="images">Server Response Time</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-server-response-time">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> <a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> worked on several tickets:
<ul>
<li>For review:
<ul>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4153" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4153</a></li>
</ul>
</li>
<li>Ready to commit:
<ul>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4211" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4211</a></li>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4129" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4129</a></li>
</ul>
</li>
<li>New tickets:
<ul>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58001" target="_blank">https://core.trac.wordpress.org/ticket/58001</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58000" target="_blank">https://core.trac.wordpress.org/ticket/58000</a></li>
</ul>
</li>
<li>My two focuses, get lazy loading meta across the line for term meta (working on comment meta) and implementing wp_cache_get_multiple in more places in core</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> work continues in the SQLite project – as well as the php autoloader for wp-core</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I’m just wrapping up an initial round of profiling observations, and plan to have something written up to share soon. Some highlights are that there are lots of places where we could try to reduce the use of file system reads associated with block registration and template rendering that we wanna look into. There is also a potential opportunity for some improvements to the way translations are being handled and classic seems that we also want to review.
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> already has some fixes in the works for some issues we discovered while comparing notes. I continue to be somewhat hampered by only being able to use one arm, but I’m working through it.</li>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a> As an aside, I noticed that the method of merging translation files in memory is probably suboptimal and we might be able to avoid that. (I’ve been reimplementing pomo in native code, and noticed it there)</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="images">Database Optimization</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-database-optimization">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> <a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> <a href="https://profiles.wordpress.org/rjasdfiii/" class="mention"><span class="mentions-prefix">@</span>rjasdfiii</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> Work continues on SQLite, next is to load woocommerce and beat on it.
<ul>
<li>Future project: identify as many places in core where the SQL is non-portable MySQL specific stuff and work on making it standard. Should that be a TRAC ticket?</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I definitely think that having trac tickets that describe any improvements you’d like to see made would be useful.</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="object-caching">JavaScript &#038; CSS</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-javascript-css">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> We are addressing the issue(s) around script concatenation, work is in progress and in the final stages of review, with minor iterations ongoing. Unit tests are being implemented to validate the approach and should be ready for final review today or tomorrow.
<ul>
<li>We are entering into a more holistic/overall code review of work done to date, essentially a code review of all work done thus far as part of the epic. Minor iteration is anticipated as part of this review process and will be executed as required.</li>
<li><a target="_blank" href="https://github.com/orgs/10up/projects/14/views/1" rel="noreferrer noopener">Work can be seen here</a></li>
<li>Various tests/testing scenarios will be undertaken prior to submitting a final pull request against.</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="measurement">Images</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-images">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I have been continuing on the lazy-loading exploration and am getting close to opening Trac tickets for the individual pieces of work
<ul>
<li>To clarify, this is about avoiding to lazy-load LCP images, or rather in-viewport images in general</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I have also been thinking a bit about the <code>fetchpriority="high"</code> feature for which we already have a module. One thing that we may need to iterate on there is that it just adds the attribute to whichever first image doesn’t have <code>loading="lazy"</code>. This is not terrible, but it’s also probably not the best way to go about it, since the two attributes should not simply be mutually exclusive. The guidance is rather:
<ul>
<li><code>fetchpriority="high"</code> should be only on the LCP image.</li>
<li><code>loading="lazy"</code> should be omitted on images above the fold (i.e. potentially more images than just the LCP image).</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I am in the very early stages of looking into ways we can improve the way WordPress calculates the <code>sizes</code> attribute.</li>
</ul>
<h3 class="wp-block-heading" id="javascript">Measurement</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-measurement">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a></p>
<ul>
<li>No updates</li>
</ul>
<h3 class="wp-block-heading">Ecosystem Tools</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-ecosystem-tools">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a> We have 2 tasks remaining for the Plugin Checker infrastructure with plans to complete this week. Once done, we will start performing initial testing and review the infrastructure holistically before working on the additional checks. Progress can be seen on the <a rel="noreferrer noopener" href="https://github.com/10up/plugin-check/" target="_blank">GitHub repo</a> here. As always, feel free to take a look and leave any thoughts/ideas you may have in the repo. Thanks!</li>
</ul>
<h3 class="wp-block-heading" id="infrastructure">Creating Standalone Plugins</h3>
<p><a href="https://github.com/WordPress/performance/issues/656">Link to GitHub overview issue</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> We’ve almost finished engineering for <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/656" target="_blank">Milestone 1</a> tasks and all <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/pulls?q=is%3Apr+is%3Aopen+label%3A%22Creating+standalone+plugins%22" target="_blank">PRs in final review</a>. If anyone has some capacity please review</li>
</ul>
<h2 class="wp-block-heading" id="infrastructure">New Projects / Proposals</h2>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Just flagging, I want to get the core unit tests running against redis. In my research, more hosts are using redis then memcache, so we could test against this and change our thinking of object caching in WP space from memcache to redis <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58000" target="_blank">https://core.trac.wordpress.org/ticket/58000</a>
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> fwiw the SQlite Object Cache plugin has extensive perf. instrumentation built in.</li>
</ul>
</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a> Re SQLite, I’m moderately concerned about the potential performance impact that introducing another layer of abstraction may introduce there. A traditional reason that WP hasn’t been DB-independent is because of (theoretical) performance gains by tightly coupling the two and taking advantage of that. (Which are assumptions I think do need to be tested.) I realise I’m coming in late to this, but I guess I’m just not seeing how the SQLite work ties into performance specifically. (I see a clear case for the non-performance benefits.)
<ul>
<li><a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> Well, I admit that the tie between SQLite and performance is a bit weird… but the way I see it, it comes down to this: on a small, lower-end server, the server’s resources are shared between a php server, apache, and a MySQL server. By using SQLite, the server can allocate its limited resources to php and therefore achieve better performance.<br />It’s better for sustainability mostly, and for performance on smaller sites (that usually are hosted on cheap servers) the performance gains will be there</li>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a> I can see how eliminating the latency and translation between two separate servers for PHP and MySQL could help performance, not sure of the overhead if it’s on the same server; that said, it feels like the primary goals of the project are not performance related</li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> It might ??? be a good idea sometime to spin off a team to do dbms-independence work, the target of which would be support for SQL Server, postgreSQL, SQLite, and, gag, Oracle. Having those would help scale up WordPress sites. postgreSQL especially because it can do wildcard searches with indexes. But that imaginary project’s connection to this team is a bit tenuous, as you mention.</li>
<li>Discussions here continued beyond the end of the meeting</li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230404T1500"><abbr class="date" title="2023-04-04T15:00:00+00:00">Tuesday, April 4, 2023 at 15: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…