You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The wp_cache_flush_runtime() in particular is quite interesting since it may be adopted by third-party plugins and libraries and expect to free up some memory, though the fallback/compat implementation does not free anything, so could result in exhausted memory errors. Since we have no way to determine whether runtime flushing is available, the work around that right now is to explicitly wp_suspend_cache_addition() for long-running (or high memory consumption) tasks, which is not ideal.
A wp_cache_flush_group() stub has also been introduced in 6.1, which should also be implemented.
Some new cache functions were introduced in WordPress 6.0:
The
wp_cache_flush_runtime()
in particular is quite interesting since it may be adopted by third-party plugins and libraries and expect to free up some memory, though the fallback/compat implementation does not free anything, so could result in exhausted memory errors. Since we have no way to determine whether runtime flushing is available, the work around that right now is to explicitlywp_suspend_cache_addition()
for long-running (or high memory consumption) tasks, which is not ideal.A
wp_cache_flush_group()
stub has also been introduced in 6.1, which should also be implemented.The two upstream projects https://github.com/pantheon-systems/wp-redis and https://github.com/alleyinteractive/wp-redis haven't seen much activity lately, although there is a ticket open for some of these cache improvements.
Acceptance criteria
wp_cache_*_multiple()
functions are implemented in our object cache forkwp_cache_flush_group()
function is implementedwp_cache_supports()
function is implemented (WordPress 6.1: https://core.trac.wordpress.org/changeset/54448)The text was updated successfully, but these errors were encountered: