<b>This week in caching: OPcache, beyond the defaults</b>

<b>This week in caching: OPcache, beyond the defaults</b>
Three reads that go past the copy-paste php.ini snippet everyone shares:
— <i>Why opcache.revalidate_freq is the wrong knob</i> — explains that on a deploy you want validate_timestamps=0 + an opcache_reset on release, not a 60s revalidate loop; clears up the most common stale-code bug.
— <i>Sizing memory_consumption with opcache_get_status()</i> — shows how to read cached_scripts vs max_cached_keys so you stop guessing at 128M; gold if you keep hitting OOM restarts.
— <i>JIT is not a cache (and won't fix your TTFB)</i> — sober take on why PHP 8 JIT helps CPU-bound math, not typical web request paths.
Credit to the PHP internals folks and Brent Roose's write-ups.
Bookmark: the opcache_get_status() walkthrough — one function call tells you if your config is actually sized right.