WP_AI_Client_Cache::get_cache_group(): string
- Since
- 7.1.0
- Source
wp-includes/ai-client/adapters/class-wp-ai-client-cache.php:39
Compatibility
- WordPress
- since 7.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 1 of the 5 tracked releases, added in 7.1.0, and compiles on PHP 7.4 through 8.6-dev.
Return value
string- Cache group name.
Performance profile
How much work a call to WP_AI_Client_Cache::get_cache_group() 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
- 7
- Plugin surface
- 1 hook
- Called by
- 8
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 7.
Third-party callbacks on 'wp_ai_client_cache_group' run inside this call, and their cost is not bounded by anything here.
8 places 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_AI_Client_Cache::get_cache_group() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 7 | 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: 7 instructions, 7 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_AI_Client_Cache::get_cache_group() runs, in this order:
- apply_filters( wp_ai_client_cache_group )filterline 51 (+12 into the body)
Filters the cache group used by the WP AI Client cache adapter.
Uses · 1
- apply_filters()Calls the callback functions that have been added to a filter hook.
Used by · 8
- WP_AI_Client_Cache::clear()Wipes clean the entire cache's keys.
- WP_AI_Client_Cache::delete()Delete an item from the cache by its unique key.
- WP_AI_Client_Cache::deleteMultiple()Deletes multiple cache items in a single operation.
- WP_AI_Client_Cache::get()Fetches a value from the cache.
- WP_AI_Client_Cache::getMultiple()Obtains multiple cache items by their unique keys.
- WP_AI_Client_Cache::has()Determines whether an item is present in the cache.
- WP_AI_Client_Cache::set()Persists data in the cache, uniquely referenced by a key with an optional expiration TTL time.
- WP_AI_Client_Cache::setMultiple()Persists a set of key => value pairs in the cache, with an optional TTL.
Source code
private function get_cache_group(): string { /** * Filters the cache group used by the WP AI Client cache adapter. * * Allows integrators to change the object cache group under which AI client * items are stored. This is useful for avoiding key collisions, creating * environment-specific caches, or adapting to backend constraints. * * @since 7.1.0 * * @param string $group The cache group. */ return (string) apply_filters( 'wp_ai_client_cache_group', self::CACHE_GROUP ); }Changelog
Introduced in 7.1.0.
Signature, return type and hooks compared across 1 parsed release.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/ai-client/adapters/class-wp-ai-client-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.