wppaste
WordPress

populate_site_meta( int $site_id, array $meta = array() )

Since
5.1.0
Source
wp-admin/includes/schema.php:1384
Creates WordPress site meta and sets the default values.

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

$site_idint
Site ID to populate meta for.
$metaarrayoptional
Custom meta $key => $value pairs to use. Default empty array.Default: array()

Performance profile

How much work a call to populate_site_meta() 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
Heavy

Reaches the database via ->query().

Scaling
Scales with input

The body loops, so the work grows with what you pass in.

Instructions
9–35

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

Plugin surface
1 hook

Third-party callbacks on 'populate_site_meta' run inside this call, and their cost is not bounded by anything here.

Called by
1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksapply_filters()called directly
  • cacheobject cachewp_cache_delete()called directly
  • sqldatabase query->query()called directly
  • optionnetwork optionget_network_option()one call below populate_site_meta()

Further down the call graph this can also reach serialize, query 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 populate_site_meta() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always9–11is_site_meta_supported()
is_site_meta_supported() && !empty($meta)34–35is_site_meta_supported(), apply_filters(), ->query(), wp_cache_delete(), wp_cache_set_sites_last_changed()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 55 instructions, 9–35 executed per call, 6 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.

Hooks and filters fired · 1

One hook fires while populate_site_meta() runs, in this order:

  1. apply_filters( populate_site_meta )filterline 1405 (+21 into the body)

    Filters meta for a site on creation.

Uses · 4

Used by · 1

Source code

function populate_site_meta( $site_id, array $meta = array() ) {	global $wpdb; 	$site_id = (int) $site_id; 	if ( ! is_site_meta_supported() ) {		return;	} 	if ( empty( $meta ) ) {		return;	} 	/**	 * Filters meta for a site on creation.	 *	 * @since 5.2.0	 *	 * @param array $meta    Associative array of site meta keys and values to be inserted.	 * @param int   $site_id ID of site to populate.	 */	$site_meta = apply_filters( 'populate_site_meta', $meta, $site_id ); 	$insert = '';	foreach ( $site_meta as $meta_key => $meta_value ) {		if ( is_array( $meta_value ) ) {			$meta_value = serialize( $meta_value );		}		if ( ! empty( $insert ) ) {			$insert .= ', ';		}		$insert .= $wpdb->prepare( '( %d, %s, %s)', $site_id, $meta_key, $meta_value );	} 	$wpdb->query( "INSERT INTO $wpdb->blogmeta ( blog_id, meta_key, meta_value ) VALUES " . $insert ); // phpcs:ignore WordPress.DB.PreparedSQL.NotPrepared 	wp_cache_delete( $site_id, 'blog_meta' );	wp_cache_set_sites_last_changed();}

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 7.1.0 tag, from src/wp-admin/includes/schema.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.