wppaste
WordPress

wp_update_user_counts( int|null $network_id = null ): bool

Since
6.0.0
Source
wp-includes/user.php:1503
Updates the total count of users on the site.

Compatibility

WordPress
since 6.0.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

$network_idint|nulloptional
ID of the network. Defaults to the current network.Default: null

Return value

bool
Whether the update was successful.

Performance profile

How much work a call to wp_update_user_counts() 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 ->get_var().

Scaling
Constant

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

Instructions
20–35

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
3

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

What it touches

  • optionnetwork optionupdate_network_option()called directly
  • sqldatabase query->get_var()called directly
  • hookthird-party callbacksdo_action()one call below wp_update_user_counts()
  • serializeserialisationmaybe_serialize()one call below wp_update_user_counts()
  • cacheobject cachewp_cache_get()one call below wp_update_user_counts()

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

WhenInstructionsCalls it makes
always20–23is_multisite(), is_multisite(), ->get_var(), update_network_option()
!is_multisite() && $network_id !== null34–35is_multisite(), __(), sprintf(), _doing_it_wrong(), is_multisite(), ->get_var(), update_network_option()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 35 instructions, 20–35 executed per call, 3 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 · 4

Used by · 3

Source code

View on Trac View on GitHub 

function wp_update_user_counts( $network_id = null ) {	global $wpdb; 	if ( ! is_multisite() && null !== $network_id ) {		_doing_it_wrong(			__FUNCTION__,			sprintf(				/* translators: %s: $network_id */				__( 'Unable to pass %s if not using multisite.' ),				'<code>$network_id</code>'			),			'6.0.0'		);	} 	$query = "SELECT COUNT(ID) as c FROM $wpdb->users";	if ( is_multisite() ) {		$query .= " WHERE spam = '0' AND deleted = '0'";	} 	$count = $wpdb->get_var( $query ); 	return update_network_option( $network_id, 'user_count', $count );}

Changelog

Introduced in 6.0.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.8.8 tag, from src/wp-includes/user.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.