WP_Object_Cache::delete( int|string $key, string $group = 'default', bool $deprecated = false ): bool
- Since
- 2.0.0
- Source
wp-includes/class-wp-object-cache.php:424
Description
If the cache key does not exist in the group, then nothing will happen.
Compatibility
- WordPress
- since 2.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
$keyint|string- What the contents in the cache are called.
$groupstringoptional- Where the cache contents are grouped. Default 'default'.Default:
'default' $deprecatedbooloptional- Unused. Default false.Default:
false
Return value
bool- True on success, false if the contents were not deleted.
Performance profile
How much work a call to WP_Object_Cache::delete() 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
- Scaling
- Constant
- Instructions
- 8–27
- Plugin surface
- None
- Called by
- 1
Reaches the database via WP_Object_Cache::delete().
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 29.
Nothing here hands control to plugin code.
1 place in core call this, so the cost is paid more often than your own code shows.
What it touches
- sqldatabase query
WP_Object_Cache::delete()this function does it
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_Object_Cache::delete() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
!->is_valid_key() | 8 | ->is_valid_key() |
->is_valid_key() | 17–27 | ->is_valid_key(), ->_exists() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 29 instructions, 8–27 executed per call, 5 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 · 2
- WP_Object_Cache::is_valid_key()Serves as a utility function to determine whether a key is valid.
- WP_Object_Cache::_exists()Serves as a utility function to determine whether a key exists in the cache.
Used by · 1
- WP_Object_Cache::delete_multiple()Deletes multiple values from the cache in one call.
Source code
public function delete( $key, $group = 'default', $deprecated = false ) { if ( ! $this->is_valid_key( $key ) ) { return false; } if ( empty( $group ) ) { $group = 'default'; } if ( $this->multisite && ! isset( $this->global_groups[ $group ] ) ) { $key = $this->blog_prefix . $key; } if ( ! $this->_exists( $key, $group ) ) { return false; } unset( $this->cache[ $group ][ $key ] ); return true; }Changelog
Introduced in 2.0.0. Unchanged from 6.7.7 through 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/class-wp-object-cache.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.