PHP: Hypertext Preprocessor (original) (raw)

opcache_invalidate

(PHP 5 >= 5.5.0, PHP 7, PHP 8, PECL ZendOpcache >= 7.0.0)

opcache_invalidate — Invalidates a cached script

Description

Parameters

filename

The path to the script being invalidated.

force

If set to [true](reserved.constants.php#constant.true), the script will be invalidated regardless of whether invalidation is necessary.

Return Values

Returns [true](reserved.constants.php#constant.true) if the opcode cache for filename was invalidated or if there was nothing to invalidate, or [false](reserved.constants.php#constant.false) if the opcode cache is disabled.

See Also

• opcache_compile_file() - Compiles and caches a PHP script without executing it
• opcache_reset() - Resets the contents of the opcode cache

Found A Problem?

joel at taotesting dot com ¶

10 years ago

`Beware that only existing files can be invalidated.

Instead of removing a file from opcache that you have delete, you need to call opcache_invalidate before deleting it.

`

dmitry dot balabka at gmail dot com ¶

5 years ago

opcache_invalidate tries to acquire SHM lock. When the lock can not be acquired opcache_invalidate will return FALSE. During multiple concurrent opcache_invalidate calls with higher probability, the function will return FALSE.

kaare at colourbox dot com ¶

9 years ago

Note that invalidation doesn't actually evict anything from the cache, it just forces a recompile. You can verify this by calling opcache_get_status() and seeing that the invalidated script is not actually removed from "scripts". This means it cannot be used as a more graceful alternative to opcache_reset() when the cache is full ("cache_full":true in status). The cache will eventually fill up and refuse to cache new requests if you do atomic deployment of PHP code by changing the web server's document root. It appears opcache_reset() is the only way to prevent this, but opcache_reset() can disable the cache for any amount of time while attempting to restart, causing load spikes.