Performance Chat Summary: 17 June 2025

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

The full chat log is available beginning here on Slack.

Open Floor

@swissspidy shared a previous question from @spacedmonkey, regarding the use of static variables in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for in-memory caching, and whether the object caching APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. with a non-persistent cache group might be a better alternative. Benefits noted included cache invalidation capabilities and improved testing scenarios.
In the original discussion thread:
- @flixos90 questioned the practical advantages of cache invalidation for non-persistent caches.
- @spacedmonkey 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.
- @flixos90 agreed that while making these caches persistent could introduce issues, improved testing practices were indeed a valid benefit.
@spacedmonkey also requested feedback on PR #8728, inviting further input from contributors.

Our next chat will be held on Tuesday, July 1, 2025 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Welcome!

Communication

Open Floor

Share this:

Site resources