wppaste
WordPress

wp_delete_all_temp_backups()

Since
6.3.0
Source
wp-includes/update.php:1125
Schedules the removal of all contents in the temporary backup directory.

Compatibility

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

Performance profile

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

Reads stored settings via get_option(), cached per request but not free on a cold cache.

Scaling
Constant

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

Instructions
13–20

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

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

  • optionoption read or writeget_option()called directly
  • hookthird-party callbacksapply_filters()one call below wp_delete_all_temp_backups()
  • cacheobject cachewp_cache_get()one call below wp_delete_all_temp_backups()
  • serializeserialisationmaybe_unserialize()one call below wp_delete_all_temp_backups()

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 · 4 distinct outcomes

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

WhenInstructionsCalls it makes
get_option()13get_option(), time(), wp_schedule_single_event()
!get_option() && !wp_doing_ajax()16get_option(), get_option(), wp_doing_ajax(), add_action()
always17get_option(), get_option(), time(), wp_schedule_single_event()
!get_option() && wp_doing_ajax()20get_option(), get_option(), wp_doing_ajax(), time(), wp_schedule_single_event()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 25 instructions, 13–20 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

Source code

function wp_delete_all_temp_backups() {	/*	 * Check if there is a lock, or if currently performing an Ajax request,	 * in which case there is a chance an update is running.	 * Reschedule for an hour from now and exit early.	 */	if ( get_option( 'core_updater.lock' ) || get_option( 'auto_updater.lock' ) || wp_doing_ajax() ) {		wp_schedule_single_event( time() + HOUR_IN_SECONDS, 'wp_delete_temp_updater_backups' );		return;	} 	// This action runs on shutdown to make sure there are no plugin updates currently running.	add_action( 'shutdown', '_wp_delete_all_temp_backups' );}

Changelog

Introduced in 6.3.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-includes/update.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.