<div style="text-align:center"></div><div>
<p><a href="https://make.wordpress.org/core/2023/02/13/performance-chat-agenda-14-february-2023/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1676390455112159">beginning here on Slack</a>.</p>
<h2 class="wp-block-heading">Announcements</h2>
<ul>
<li><a href="https://github.com/WordPress/performance/issues/631">Performance team roadmap for 2023</a> reminder, 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 <strong>Wednesday February 15, 2023</strong></li>
<li><a href="https://make.wordpress.org/performance/2023/02/01/core-performance-team-rep-updates/">Team rep nomination</a> reminder, please add your nominations for Performance Team Rep by <strong>Friday, February 24 2023</strong></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/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: we got the lazy-loading fix for block themes committed to WordPress core yesterday: <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/changeset/55318" target="_blank">https://core.trac.wordpress.org/changeset/55318</a> – just in time for the WP 6.2 Beta 2</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> (10 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>: Would like to get feedback on <a href="https://core.trac.wordpress.org/ticket/57701">#57701</a> and Gutenberg PRs <a href="https://github.com/WordPress/gutenberg/pull/48003">48003</a>, <a href="https://github.com/WordPress/gutenberg/pull/48001">48001</a>, <a href="https://github.com/WordPress/gutenberg/pull/48000">48000</a>, <a href="https://github.com/WordPress/gutenberg/pull/47999">47999</a>, <a href="https://github.com/WordPress/gutenberg/pull/47997">47997</a></li>
</ul>
<h4 class="wp-block-heading" id="feedback-requested-2">Feedback requested</h4>
<ul>
<li>See above</li>
<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>: Progress on the Plugin Checker infrastructure is moving along nicely. We’re aiming to have a working plugin running with some initial checks by end of the month. You can track progress on the <a rel="noreferrer noopener" href="https://github.com/10up/plugin-check/" target="_blank">GitHub repo</a> and feel free to leave any thoughts/ideas you may have (the repo will be moved to the WordPress organisation when ready).</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: I’ve got a working implementation of a profiler setup, using XHProf in a wp-env environment that I plan on cleaning up and submitting as a PR to the <code>@wordpress/env</code> package this week and will write up detailed instructions for how others can use these tools to profile WordPress locally.</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: I’ve also been supporting @mukesh27 (who is also traveling today) on an initial implementation of adding automated server timing measurements to the wordpress-develop repo so we could begin measuring the performance impact of specific commits to core. Looking to try and open a PR later this week.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I quickly hacked the WP core dev environment yesterday using <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>‘s XHProf approach above to get it running there too: <a rel="noreferrer noopener" href="https://github.com/felixarntz/wordpress-develop/commit/ed096270d817eb9850ea54e4a30662cf2d9492d8" target="_blank">https://github.com/felixarntz/wordpress-develop/commit/ed096270d817eb9850ea54e4a30662cf2d9492d8</a><br />This is by no means a clean implementation, but something to potentially explore later; would be nice to get this optionally baked into the core dev environment as well so we can easily do profiling as we develop</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: One thing to note there is that there is an observability cost to profiling, so it’s not meant to be a way of measuring performance from a user’s point of view, but instead to inspect the performance attributes of specific subsystems within a WordPress request lifecycle</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>No updates</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>: SQLite integration: Lots of testing coming in. Ari Stathopoulos and Adam Zielinski have been hammering away on the SQL dialect translation issues. <a href="https://github.com/WordPress/sqlite-database-integration/pull/9">This PR</a> will be an ongoing job.</li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a>: It would be nice to integrate some database query stuff into the Server-Timing API — that reports to the browser. I’ll do a module proposal.</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/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Reminder that next Monday Feb 20 is the PL 2.0.0 release (<a href="https://github.com/WordPress/performance/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.0.0">PRs still open in the milestone</a> need to be completed by this Wednesday Feb 15, or they will be punted to a future release)</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: As always, the 2.0.0 release will happen as part of our regular release party chat – please join <a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a> and others <strong>next <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230220T1800"><abbr class="date" title="2023-02-20T18:00:00+00:00">Monday, February 20, 2023 at 18:00 UTC</abbr></a> here in <a href="https://wordpress.slack.com/archives/C02KGN5K076">#core-performance</a></strong> to get the release out! Any support and testing is much appreciated.</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> (7 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>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li>Approach for <a href="https://github.com/WordPress/performance/issues/618#issuecomment-1411829392">publishing modules as standalone plugins</a>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: That seems like a conversation about “which” modules should be published outside the Performance lab plugin, which is the same as <a href="https://github.com/WordPress/performance/issues/640">this issue</a>, correct?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Yes 640 is related, but this is about our policy. Basically, if we decide every module is a standalone plugin, there will never need to be any discussions on which modules to publish and which not to</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: I think the only thing that is unclear is whether we’re going to intentionally <em>not</em> publish certain types of modules (e.g., site health checks) as separate individual plugins. I’m still of the opinion that those types of features, which don’t modify the user experience of WordPress, but are instead meant to help measure and/or provide performance feedback should remain part of the Performance Lab plugin itself, rather than being shipped separately.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: So I guess we have to decide <a href="https://github.com/WordPress/performance/issues/618#issuecomment-1430098628">between 3 alternatives</a></li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: I think that’s a good initial set of options. As a thought experiment, we should apply these options to the current list of modules</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I took your request to heart and posted a <a href="https://github.com/WordPress/performance/issues/640#issuecomment-1430107670">list of modules here</a></li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230221T1600"><abbr class="date" title="2023-02-21T16:00:00+00:00">Tuesday, February 21, 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…