<div style="text-align:center"></div><div>
<p><a href="https://make.wordpress.org/core/2024/03/12/performance-chat-agenda-12-march-2024/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1710259213872169">beginning here on Slack</a>.</p>
<h1 class="wp-block-heading">Announcements</h1>
<ul>
<li>Welcome to our new members of <a href="http://wordpress.slack.com/messages/core-performance/">#core-performance</a></li>
<li>Reminder on timezone difference for the next 3 weeks, this chat will remain at 16:00 UTC, then it will switch to 15:00 UTC from April 2</li>
</ul>
<h1 class="wp-block-heading" id="focus-group-updates">Priority Items</h1>
<p>Structure:</p>
<ul>
<li>WordPress performance Trac tickets discussion</li>
<li>Performance Lab plugin (and other performance plugins) discussion</li>
<li>Active priority projects
<ul>
<li>Plugin checker</li>
<li>Improve template loading</li>
<li>INP opportunities research</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="images">WordPress Performance Trac Tickets</h2>
<ul>
<li>For WordPress 6.5:
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> opened <a href="https://core.trac.wordpress.org/ticket/60749">#60749</a>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> asked if this is mostly a memory win?</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> It does seem to be less of an impact on IWT than what I was measuring on Friday. Still not sure what the difference is there, or if there is some caching in play that I had disabled on Friday. Even so, it does make a positive impact and memory consumption can lead to slower IWT. The other place that could use more eyes is trying to identify opportunities to improve the performance of the Navigation block, which went through a bigger refactor during this release, which is leading to longer rendering times. I don’t think we’ve identified any particular flaw thus far</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> working on the ongoing research on potential performance regression that I think is still unresolved [<a href="https://wordpress.slack.com/archives/C02KGN5K076/p1709678536541849" data-type="link" data-id="https://wordpress.slack.com/archives/C02KGN5K076/p1709678536541849">link</a>]</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> will plan on doing another set of benchmarks for RC 2 once it has been released, and can continue</li>
</ul>
</li>
<li>For Future Releases:
<ul>
<li>We already have <a href="https://core.trac.wordpress.org/query?status=accepted&#038;status=assigned&#038;status=closed&#038;status=new&#038;status=reopened&#038;status=reviewing&#038;focuses=~performance&#038;milestone=6.6&#038;groupdesc=1&#038;group=resolution&#038;col=id&#038;col=summary&#038;col=status&#038;col=milestone&#038;col=owner&#038;col=type&#038;col=priority&#038;col=keywords&#038;order=priority" target="_blank" rel="noreferrer noopener">16 items in the 6.6 milestone</a>, but it’s a good time for folks to start thinking about what they are wanting to focus on for the next release.</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="images">Performance Lab Plugin (and other Performance Plugins)</h2>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> posted an update on what’s next for 3.0 of the Performance Lab plugin:
<ul>
<li>There are a couple new issues defined for the 3.0.0 milestone:</li>
<li><a href="https://github.com/WordPress/performance/issues/1029" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1029</a> (PR in progress)</li>
<li><a href="https://github.com/WordPress/performance/issues/1030" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1030</a> (ready for engineering once 1029 PR has been merged)</li>
<li><a href="https://github.com/WordPress/performance/issues/1031" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1031</a> (ready for PR)</li>
<li><a href="https://github.com/WordPress/performance/issues/1032" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1032</a> (requires further discussion)</li>
<li><a href="https://github.com/WordPress/performance/issues/1045" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1045</a> (ready for PR once 1031 PR has been merged)</li>
<li><a href="https://github.com/WordPress/performance/issues/1046" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1046</a> (requires further discussion, not engineering related)</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> has 2 PRs ready for review:
<ul>
<li>PR <a href="https://github.com/WordPress/performance/pull/1049" target="_blank" rel="noreferrer noopener">#1049</a> – Fix <code>test-plugins</code> command</li>
<li>PR <a href="https://github.com/WordPress/performance/pull/1048" target="_blank" rel="noreferrer noopener">#1048</a> – Support changing autoload value for largest autoloaded options</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="object-caching">Active Priority Projects</h2>
<h3 class="wp-block-heading">Plugin Checker</h3>
<ul>
<li>Mostly quiet since the 1.0 release. There is the start of a 1.1 milestone, but I think the folks involved in next steps here have been mostly busy with WC Asia and 6.5 release work.</li>
</ul>
<h3 class="wp-block-heading" id="measurement">Improve template loading</h3>
<ul>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> is exploring other parts of the ticket <a href="https://core.trac.wordpress.org/ticket/59600">#59600</a> PR <a href="https://github.com/WordPress/wordpress-develop/pull/6137" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/wordpress-develop/pull/6137</a></li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I see that there is some feedback from <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> that needs to resolve about the filter in <a href="https://github.com/WordPress/wordpress-develop/pull/6137" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/wordpress-develop/pull/6137</a></li>
<li><a href="https://profiles.wordpress.org/thelovekesh/" class="mention"><span class="mentions-prefix">@</span>thelovekesh</a> PR for 1029 is ready for further review. Also, PR for this issue alters anything related to Site health and not modules.
<ul>
<li>Asked <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://github.com/WordPress/performance/pull/1042#pullrequestreview-1930761224">https://github.com/WordPress/performance/pull/1042#pullrequestreview-1930761224</a>, can we keep this the part of PR where we remove modules completely? <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> already replied</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="javascript">INP research opportunities</h3>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Last item in our active priority projects list: INP opportunities research. I believe @adamsilverstein recently did some research on this, but am unsure if there is anything ready to be shared yet. We can pick this up in a future meeting. That is a good reminder to everyone that INP became a Core Web Vital starting today: <a href="https://web.dev/blog/inp-cwv-march-12" target="_blank" rel="noreferrer noopener">https://web.dev/blog/inp-cwv-march-12</a>
<ul>
<li>One of our team goals for this year is to find ways to improve WP this metric, so it’s good to keep in mind.</li>
</ul>
</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/thelovekesh/" class="mention"><span class="mentions-prefix">@</span>thelovekesh</a> asked Currently when we do a plugin release it triggers two workflows:
<ul>
<li>PL plugin release</li>
<li>and Standalone plugin release.</li>
<li>Do we always need to trigger the workflow for standalone plugins?</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> By default, new versions of standalone plugins are triggered together with the PL plugin release. Other than that, it would need to be the manual workflow. That’s how it works now. There’s certainly things that can be improved. We need to rethink our release strategy, for instance also whether we want to have releases of the standalone plugins tagged on GitHub in addition, which right now is missing</li>
<li><a href="https://profiles.wordpress.org/thelovekesh/" class="mention"><span class="mentions-prefix">@</span>thelovekesh</a> We might need to streamline release notes for PL and standalone plugins. Currently we are including them for PL plugin. With <a href="https://github.com/WordPress/performance/pull/1033" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/pull/1033</a>, we are attaching all release assets on specific release.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Right, the changelog generator also only works for PL right now.</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> is working down this list in age order to review/renew [<a href="https://core.trac.wordpress.org/query?status=accepted&#038;status=assigned&#038;status=new&#038;status=reopened&#038;status=reviewing&#038;focuses=~performance&#038;order=priority" data-type="link" data-id="https://core.trac.wordpress.org/query?status=accepted&#038;status=assigned&#038;status=new&#038;status=reopened&#038;status=reviewing&#038;focuses=~performance&#038;order=priority">link</a>]
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I gave your PR for limiting autoloaded options size another review last week, it looks really good, just a few minor things. Have you been able to take a look at that? I’d love to commit this early in the 6.6 cycle</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Something else that would be helpful is that if you run across an issue that you think should be prioritized because it makes a big impact to improve overall performance for end users, please share it in the channel so we can get more eyes on it and get it into a milestone.</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> will start with these tickets <strong><a href="https://core.trac.wordpress.org/ticket/18836" target="_blank" rel="noreferrer noopener">18836</a></strong> <a href="https://core.trac.wordpress.org/ticket/18836" target="_blank" rel="noreferrer noopener">ORDER BY RAND() is slow</a><br />If we can get some modified SQL that works</li>
</ul>
</li>
<li><strong>REMINDER: </strong>This meeting will continue at 16:00 UTC for the next 3 weeks, then it will switch to 15:00 UTC from April 2 onwards</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240319T1600"><abbr class="date" title="2024-03-19T16:00:00+00:00">Tuesday, March 19, 2024 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-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>

As October winds down, so too does Blocktober, Tammie Lister’s month-long challenge to create a…
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…