wppaste
WordPress

wp_maybe_clean_new_site_cache_on_update( WP_Site $new_site, WP_Site $old_site )

Since
5.1.0
Source
wp-includes/ms-site.php:1272
Cleans the necessary caches after specific site data has been updated.

Compatibility

WordPress
since 5.1.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$new_siteWP_Site
The site object after the update.
$old_siteWP_Site
The site object prior to the update.

Performance profile

How much work a call to wp_maybe_clean_new_site_cache_on_update() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Light

Only touches the object cache, via wp_cache_delete().

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
10–14

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 14.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

  • cacheobject cachewp_cache_delete()one call below wp_maybe_clean_new_site_cache_on_update()
  • hookthird-party callbacksdo_action()one call below wp_maybe_clean_new_site_cache_on_update()

Further down the call graph this can also reach query, option, serialize and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 2 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_maybe_clean_new_site_cache_on_update() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always10–14clean_blog_cache()
always11none

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 14 instructions, 10–14 executed per call, 2 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 1

Source code

View on Trac View on GitHub 

function wp_maybe_clean_new_site_cache_on_update( $new_site, $old_site ) {	if ( $old_site->domain !== $new_site->domain || $old_site->path !== $new_site->path ) {		clean_blog_cache( $new_site );	}}

Changelog

Introduced in 5.1.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 6.7.7 tag, from src/wp-includes/ms-site.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.