Performance Chat Summary: 17 June 2025

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 capabilitiescapability A capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). 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