<div>
<p>The full chat log is available beginning <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1750172425472579" data-type="link" data-id="https://wordpress.slack.com/archives/C02KGN5K076/p1748962825207989">here on Slack</a>.</p>
<h2 class="wp-block-heading"><strong>Open Floor</strong></h2>
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a><strong> </strong>shared a previous question from <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>, regarding the use of static variables in core for in-memory caching, and whether the object caching API with a non-persistent cache group might be a better alternative. Benefits noted included cache invalidation capabilities and improved testing scenarios.<br />In the original discussion thread:
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> questioned the practical advantages of cache invalidation for non-persistent caches.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> clarified it would allow developers to optionally enable persistent caching, improve testability by clearing caches between tests, and align with the intended usage of the object cache API.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> agreed that while making these caches persistent could introduce issues, improved testing practices were indeed a valid benefit.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> also requested feedback on <a class="" href="https://github.com/WordPress/wordpress-develop/pull/8728">PR #8728</a>, inviting further input from contributors.</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250701T1500"><abbr class="date" title="2025-07-01T15:00:00+00:00">Tuesday, July 1, 2025 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>
<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/hosting/" class="tag"><span class="tag-prefix">#</span>hosting</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 second Release Candidate (“RC2”) for WordPress 6.9 is ready for download and testing! This…
This post is the latest in a series of updates focused on the performance improvements…
The first Release Candidate (“RC1”) for WordPress 6.9 is ready for download and testing! This…
This story was produced in collaboration with Mark Szymanski and Adam Weeks. Check out Mark’s…
WordPress is moving closer to Google Docs-style collaborative editing. In an update on Phase 3…
The WordPress Foundation’s bid to trademark “Managed WordPress” and “Hosted WordPress” in the United States…