WP_Feed_Cache_Transient::__construct( string $location, string $name, Base::TYPE_FEED|Base::TYPE_IMAGE $type )
- Since
- 2.8.0, 3.2.0, 6.7.0
- Source
wp-includes/class-wp-feed-cache-transient.php:58
Compatibility
- WordPress
- since 6.7.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
$locationstring- URL location (scheme is used to determine handler).
$namestring- Unique identifier for cache object.
$typeBase::TYPE_FEED|Base::TYPE_IMAGE- Either
TYPE_FEED('spc') for SimplePie data, orTYPE_IMAGE('spi') for image data.
Performance profile
How much work a call to WP_Feed_Cache_Transient::__construct() 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
- Trivial
- Scaling
- Constant
- Instructions
- 18
- Plugin surface
- 1 hook
- Called by
- 1
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5. The body compiles to 18.
Third-party callbacks on 'wp_feed_cache_transient_lifetime' run inside this call, and their cost is not bounded by anything here.
1 place in core call this, so the cost is paid more often than your own code shows.
What it touches
- hookthird-party callbacks
apply_filters()called directly
What one call costs · 1 distinct outcome
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Feed_Cache_Transient::__construct() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 18 | apply_filters() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 18 instructions, 18 executed per call, 0 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 WP_Feed_Cache_Transient::__construct() runs, in this order:
- apply_filters( wp_feed_cache_transient_lifetime )filterline 71 (+13 into the body)
Filters the transient lifetime of the feed cache.
Uses · 1
- apply_filters()Calls the callback functions that have been added to a filter hook.
Used by · 1
- WP_Feed_Cache::create()Creates a new SimplePie\Cache object.
Source code
public function __construct( $location, $name, $type ) { $this->name = 'feed_' . $name; $this->mod_name = 'feed_mod_' . $name; $lifetime = $this->lifetime; /** * Filters the transient lifetime of the feed cache. * * @since 2.8.0 * * @param int $lifetime Cache duration in seconds. Default is 43200 seconds (12 hours). * @param string $name Unique identifier for the cache object. */ $this->lifetime = apply_filters( 'wp_feed_cache_transient_lifetime', $lifetime, $name ); }Changelog
Introduced in 2.8.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
SimplePie\Cache\Base interface.from the docblockAbout this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/class-wp-feed-cache-transient.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.