<div style="text-align:center"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==" fifu-lazy="1" fifu-data-sizes="auto" fifu-data-srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="497" height="292" fifu-data-src="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance team meeting summary 30 August 2022" title="Performance team meeting summary 30 August 2022" srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1 497w, https://www.awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day-300x176.png 300w" sizes="(max-width: 497px) 100vw, 497px" /></div><div>
<p><a href="https://make.wordpress.org/core/2022/08/26/performance-chat-agenda-30-august-2022/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1661871640706189">beginning here on Slack</a>.</p>
<h2>Announcements</h2>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: multiple announcements
<ul>
<li><a href="https://make.wordpress.org/performance/2022/08/09/core-performance-team-rep-nominations/">Team Rep nominations reminder</a></li>
<li>If you are contributing to the <code>WordPress/performance</code> GitHub repository (or any WordPress GitHub repository FWIW), please link your WordPress.org and GitHub accounts if you haven’t done so. You can do so at <a href="https://profiles.wordpress.org/profile/profile/edit/group/1/">https://profiles.wordpress.org/profile/profile/edit/group/1/</a></li>
<li>If you have been contributing to the team’s efforts (e.g. GitHub, discussions, conversations in this chat, …) but don’t have the “Performance Contributor” badge on your profile, you may request to have it added by requesting to join the group at <a href="https://profiles.wordpress.org/associations/performance-contributor/">https://profiles.wordpress.org/associations/performance-contributor/</a></li>
<li>If you are contributing to the <code>WordPress/performance</code> GitHub repository, please be aware of a new rule to <strong>avoid naming your regular temporary coding branches something like <code>feature/</code></strong>. That <code>feature/</code> prefix will be reserved for special protected feature branches going forward
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: other than the ‘feature/’ prefix, are there any other conventions we want to follow / is that documented somewhere?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Only <code>feature/</code> and <code>release/</code> must not be used for regular coding branches (a <a href="https://github.com/WordPress/performance/pull/508">pull request</a> to document this has since been opened)</li>
</ul>
</li>
</ul>
</li>
</ul>
<h2 id="focus-group-updates">Focus group updates</h2>
<h3 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>: we have been working on responding to feedback on the WebP ticket (<a href="https://core.trac.wordpress.org/ticket/55443">#55443</a>) and conducting research around the potential usefulness of a “threshold” size above which jpegs would be generated instead of WebPs. The research used WP-CLI to run many images through WordPress image compression with WebP quality set at 82, 84 &#038; 86 to investigate how often WebP images are larger than the JPEG equivalent, at what image dimensions, and by how much. I will be summarizing the research in my response on the ticket shortly
<ul>
<li>there seems to be strong agreement that we should only output a single mime type. The main question now is if the mult-mime support is worth keeping – the code adds a good bit of complexity to media, and isn’t strictly required for the approach we are considering now… so we are trying to weigh the pros and cons of keeping it. It might make sense to revert and re-introduce when we have support for async media generation (something we are already working on)</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a>: Working on creating sub-issues with implementation details for <a rel="noreferrer noopener" href="https://github.com/wordpress/performance/issues/24" target="_blank">Regenerate existing images</a> and core patch for <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/3074" target="_blank">Update core functions to support multiple mime types</a></li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a>: Working on WebP core follow-up patch <a href="https://github.com/WordPress/wordpress-develop/pull/3036">https://github.com/WordPress/wordpress-develop/pull/3036</a> and Core Trac ticket with performance focus</li>
<li><a href="https://profiles.wordpress.org/wpgurudev/" class="mention"><span class="mentions-prefix">@</span>wpgurudev</a>: Basic <code>regenerate-existing-images</code> module PR has been merged, <a href="https://github.com/WordPress/performance/pull/497">follow-up PR</a> for background job taxonomy up for final review; <a href="https://github.com/WordPress/performance/pull/507">background job class PR</a> is ready, waiting for taxonomy PR to get merged, so that tests can be added</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: <a href="https://make.wordpress.org/core/2022/07/21/proposal-add-a-dominant-color-background-to-images/">Dominant color</a> is getting pushback; would like to suggest that we put it behind a theme feature flag (show-dominant-color) and we add it to the media library in wp-admin
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: We should evaluate that pushback closely. Can you elaborate why it should be controlled by the theme instead?</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: The push back seems to have the theme of “we like this but themes should control the look and feel”</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: So it would mean the data is still added to every image upload, but the theme decides how to use that color information? Sounds reasonable</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: discussing this further will be made a dedicated agenda item next week</li>
</ul>
</li>
</ul>
<h4 id="feedback-requested">Feedback requested</h4>
<ul>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22">Needs Discussion</a><span style="color: initial;, sans-serif"> (9 issues)</span></li>
</ul>
<h3 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/tillkruess/" class="mention"><span class="mentions-prefix">@</span>tillkruess</a>: focus had one core merge last week (see <a href="https://github.com/WordPress/wordpress-develop/pull/3011">PR</a> / <a href="https://core.trac.wordpress.org/changeset/53941">changeset</a>), with great results already (see chart from wordpress.org below, shared by <a href="https://profiles.wordpress.org/dd32/" class="mention"><span class="mentions-prefix">@</span>dd32</a>)</li>
</ul>
<div class="wp-block-image">
<figure class="aligncenter size-full"><a href="https://awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==" fifu-lazy="1" fifu-data-sizes="auto" fifu-data-srcset="https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" data-attachment-id="98375" data-permalink="https://make.wordpress.org/core/2022/08/30/performance-team-meeting-summary-30-august-2022/mysql_bytes-day/#main" data-orig-file="https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1" data-orig-size="497,292" data-comments-opened="1" data-image-meta='{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}' data-image-title="mysql_bytes-day" data-image-description="" data-image-caption="" data-medium-file="https://make.wordpress.org/core/files/2022/08/mysql_bytes-day-300x176.png" data-large-file="https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1" decoding="async" width="497" height="292"src="https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1" alt="MySQL throughput dropping from roughly 1.5M to pretty much half following the commit" class="wp-image-98375" srcset="https://i1.wp.com/awordpresscommenter.com/wp-content/uploads/2022/08/mysql_bytes-day.png?ssl=1 497w, https://make.wordpress.org/core/files/2022/08/mysql_bytes-day-300x176.png 300w" sizes="(max-width: 497px) 100vw, 497px"></a></figure>
</div>
<h4 id="feedback-requested-2">Feedback requested</h4>
<ul>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+">Needs Discussion</a><span style="color: initial;, sans-serif"> (3 issues)</span></li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+">Needs Review</a> (1 issue)</li>
</ul>
<h3 id="site-health">Site Health</h3>
<p>N/A</p>
<p><a href="https://github.com/WordPress/performance/projects/4">GitHub project</a></p>
<ul>
<li><strong>We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack</strong></li>
<li><a href="https://profiles.wordpress.org/furi3r/" class="mention"><span class="mentions-prefix">@</span>furi3r</a>: persistent object cache Site Health <a href="https://github.com/WordPress/wordpress-develop/pull/2890">PR</a> was merged (see <a href="https://core.trac.wordpress.org/changeset/53955">changeset</a> / <a href="https://core.trac.wordpress.org/ticket/56040">ticket</a>), what is left for the full page cache <a href="https://github.com/WordPress/wordpress-develop/pull/2894">PR</a> (see <a href="https://core.trac.wordpress.org/ticket/56041">ticket</a>)?
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: haven’t re-reviewed it yet since last week, but if all the feedback from then has been addressed and the merge conflicts are fixed, this should be good to go</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/furi3r/" class="mention"><span class="mentions-prefix">@</span>furi3r</a>: can try to get a Draft for the dev notes by next week, I’ll be on holiday after that, so maybe someone can take over if not ready/published</li>
</ul>
<h4 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%2F4+">Needs Discussion</a> (9 issues)</li>
</ul>
<h3 id="measurement">Measurement</h3>
<p>N/A</p>
<p><a href="https://github.com/WordPress/performance/projects/5">GitHub project</a></p>
<ul>
<li><strong>We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack</strong></li>
<li><a href="https://profiles.wordpress.org/mehulkaklotar/" class="mention"><span class="mentions-prefix">@</span>mehulkaklotar</a>: working on proposal for Plugin Check plugin</li>
</ul>
<h4 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 id="javascript">JavaScript</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/pushpakpop/" class="mention"><span class="mentions-prefix">@</span>pushpakpop</a>: we have started research around the approach for the JavaScript orchestration project</li>
</ul>
<h4 id="feedback-requested-3">Feedback requested</h4>
<ul>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+">Needs Discussion</a><span style="color: initial;, sans-serif"> (2 issues)</span></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> (3 issues)</li>
</ul>
<h2 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>: <a href="https://github.com/WordPress/performance/pull/437">PR</a> to fix unexpected input <code>Warning</code> message during release build/test process ready for re-review</li>
</ul>
<h4 id="feedback-requested-1">Feedback requested</h4>
<ul>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+">Needs Discussion</a><span style="color: initial;, sans-serif"> (5 issues)</span></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> (4 issues)</li>
</ul>
<h2>Open Floor</h2>
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a>: <a href="https://github.com/WordPress/performance/issues/475">Database Performance Health Checks module proposal</a> (continued from last week)
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a>: Is DBMS server performance part of the mission of this group?
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Absolutely! Every aspect of performance is relevant to the team’s mission</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> revised this health-check module proposal to simplify the output (see <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/475" target="_blank">https://github.com/WordPress/performance/issues/475</a> and please look at the “Other” section), agrees with last week’s conversation about excess complexity; we’ll do all the checks and only report the trouble spots
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: In that case I’d argue there is still a lot of complexity. Implementing each of these tests in a reliable way is probably not trivial. To clarify, I’m not saying we <em>shouldn’t</em> do it. I’m only suggesting we start with only one of them for the first version and add the others in additional iterations</li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a>: FWIW I have a prototype I’ve been testing against old versions of DBMS software as well as new versions. The tests were designed to cope with missing RDBMS features in the old versions. Yeah, complex, for sure. But doable.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Does anybody have objections against this module proposal?
<ul>
<li>Quick survey of thumbs up / thumbs down resulted in <strong>9 thumbs up and 0 thumbs down</strong></li>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> will start a pull request introducing the module; if it shows that some bits there are too complex to get through in a reasonable time, we can still re-assess if we want to narrow down the scope</li>
</ul>
</li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220906T1500"><abbr class="date" title="2022-09-06T15:00:00+00:00">Tuesday, September 6, 2022 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/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>

A U.S. magistrate judge has moved to rein in the escalating discovery battle between WP…
Ollie’s “game-changing” Menu Designer plugin is moving toward inclusion in WordPress core. Anne McCarthy says…
WordPress.com has rolled out support for the Model Context Protocol (MCP), allowing AI assistants to…
Ten hosting providers have been certified under the Secure Hosting Alliance’s new Trust Seal program,…
When WP Accessibility Day kicks off next week, someone, somewhere will always be awake. As…
The full chat log is available beginning here on Slack. WordPress Performance Trac tickets @westonruter…