#opcache,
📦 vursion/laravel-opcache 1.5.0

laravel-opcache

🔗 https://github.com/vursion/laravel-opcache
November 21, 2026 at 10:12 AM
📦 v3sp/v3cache v0.2.2

Monitoring, health checking, warmup and optimization for PHP OPcache

🔗 https://github.com/V3sp/v3cache
November 21, 2026 at 6:15 PM
🔧 Requirements: PHP 8.4 or 8.5, PHPUnit 13.3+. Not supported: Windows, PHP-FPM and web SAPIs. Cannot run alongside Xdebug, PCOV or opcache JIT, preload or file cache. MIT licensed.
November 21, 2026 at 4:51 PM
📦 tevkert/queue-prefork v1.2.0

Cut the memory of Laravel queue workers by up to 80 %: queue:work and Horizon workers run as forks of one template that shares compiled code through opcache. Drop-in, no code changes.

🔗 https://github.com/tevkert/queue-prefork
November 20, 2026 at 5:11 PM
Anyone running MediaWiki runs into the word cache all over the configuration files and documentation. OPcache, APCu, memcached, the parser cache, the localisation cache, the file cache and the CDN: there are so many names that it is easy to lose track of which one holds what. Most of it is […]
Original post on femiwiki.com
femiwiki.com
November 20, 2026 at 11:58 PM
📦 tevkert/queue-prefork v1.1.1

Cut the memory of Laravel queue workers by up to 80 %: queue:work and Horizon workers run as forks of one template that shares compiled code through opcache. Drop-in, no code changes.

🔗 https://github.com/tevkert/queue-prefork
November 19, 2026 at 8:19 AM
📦 tevkert/queue-prefork v1.1.0

Cut the memory of Laravel queue workers by up to 80 %: queue:work and Horizon workers run as forks of one template that shares compiled code through opcache. Drop-in, no code changes.

🔗 https://github.com/tevkert/queue-prefork
November 18, 2026 at 5:59 PM
Deployed Laravel, still serving old code? With validate_timestamps=0 PHP keeps old bytecode, and artisan can't reset FPM's OPcache. Kiln clears and warms it from inside an FPM worker. Free, MIT. https://amjad.com.pk/laravel/packages/kiln
November 17, 2026 at 4:30 PM
外に公開しているDebian stableのphp上げた

$ sudo apt update && sudo apt upgrade
g$ php -v
PHP 8.4.28 (cli) (built: Nov 18 2026 10:55:31) (NTS)
Copyright (c) The PHP Group
Built by Debian
Zend Engine v4.4.28, Copyright (c) Zend Technologies
with Zend OPcache v8.4.28 […]
Original post on snac.matoken.org
snac.matoken.org
November 19, 2026 at 8:37 PM
Programiści #PHP pewnie znają takie terminy jak #opcache, #JIT czy #AOT (te dwa ostatnie być może są znane także inżynierom pracującym w innych technologiach). Ale czy każdy wie, czym właściwie są i się różnią? O tym w tym artykule.

#programowanie
Raw PHP, opcache, JIT, and AOT: what actually happens to your code
A few weeks ago, I posted a carousel on LinkedIn about TypePHP, the ahead-of-time compiler the Swoole...
dev.to
November 16, 2026 at 9:00 AM
I'd test the next PHP on a staging copy with the same plugins and with OPcache on, not only a syntax check. Old plugins often fail on dynamic properties or a return type only after the code has actually been warmed up.
November 17, 2026 at 2:58 PM
The Three Layers of WordPress Caching: Page Cache, Object Cache, and OPcache
"I cleared the cache and it's still wrong." "I installed a caching plugin, but the admin screen doesn't change." These are common questions in WordPress maintenance, and the cause is often that several different layers are being treated as one thing called "the cache." Around a WordPress site there are at least three distinct caches: the **page cache** , the **object cache** , and **OPcache**. They differ in what they store, where it lives, and how you clear it. This article sorts out the three and how to tell them apart. It describes general WordPress and PHP behavior, not any specific product. > Note: The transient API and Cache-Control / ETag are covered in separate articles. This one stays on the three server-side layers. ## The big picture Following a request from arrival to display, roughly from top to bottom: Layer | What it stores | Where | What it saves ---|---|---|--- Page cache | The finished HTML of a page | Disk or memory | PHP can be skipped almost entirely Object cache | Results of database queries and option values | Memory (per request by default) | PHP runs, but fewer DB queries OPcache | Compiled PHP code | PHP's shared memory | PHP files are not re-read and re-parsed The key point: **the higher the layer, the earlier it ends the work.** A page cache hit barely touches PHP or the database. An object cache hit still runs PHP but reduces DB queries. OPcache doesn't change whether PHP runs; it only avoids re-parsing PHP source each time. ## 1. Page cache: saving the finished HTML A page cache stores the HTML WordPress has already assembled and serves it for the next request to the same URL. If logged-out visitors read the same post, there's no need to run the theme and plugins and query the database every time. It can live in several places: * A caching plugin writes HTML files to disk and the web server serves them directly * The web server side (reverse proxy, FastCGI cache, and so on) holds them * A mechanism provided by the hosting company holds them Three properties worth remembering: 1. **It isn't suited to pages that differ per visitor.** Logged-in screens, carts, and form results are normally excluded. 2. **Stale content can remain.** After you update a post, the old HTML is served until the cache entry is discarded. Many plugins purge the affected page on update, but a theme or widget change may need a full purge. 3. **The admin area is generally excluded.** If the admin screen looks stale, the page cache is often not the cause. ## 2. Object cache: reusing the database's answers A single page view makes WordPress fetch many values: the site name, theme settings, post lists, user data. Many live in the database, and querying each time is slow. WordPress core therefore includes a built-in in-memory store (`WP_Object_Cache`) that reuses fetched values. Functions like `wp_cache_get()` and `wp_cache_set()` are its entry points. However, **by default this cache disappears when the request ends.** It only helps within a single page view; the next request queries the database again. A _persistent_ object cache keeps values across requests. You provide an external in-memory store such as Redis or Memcached and connect it through the `wp-content/object-cache.php` drop-in. Then later requests also make fewer DB queries. How to tell, and what to watch for: * Check for `wp-content/object-cache.php`, or run `wp cache type` in WP-CLI * Because values live outside the database, **editing the database directly may not show on screen while the cache still holds the old value** * `wp cache flush` clears it, but if several sites share one store, it can affect the others. Check first in shared environments. ## 3. OPcache: saving the PHP code itself The first two cache data that WordPress produces or fetches. OPcache is different: it caches **the PHP code itself.** PHP source is converted from text into internal instructions (opcodes) on each run. OPcache keeps the result in shared memory and skips the conversion next time. For an application with many PHP files like WordPress, this matters. It ships as a standard PHP extension and is enabled by default on many shared hosts. The trap for maintainers: **editing a file may not take effect immediately.** OPcache has settings for how often it checks file modification times (such as `opcache.revalidate_freq`), and old code can keep running in between. In environments with timestamp checking turned off (`opcache.validate_timestamps=0`), old code runs until PHP is restarted or the cache is reset. If you replaced a plugin or theme PHP file and behavior didn't change, suspect this layer. You reset it by reloading PHP-FPM or using a reset function in the hosting control panel. Note that WP-CLI's `wp cache flush` does not clear OPcache. That command operates on the object cache, a different layer. ## When "I cleared it and it's still wrong" By symptom, which layer to suspect first: Symptom | Suspect first ---|--- Visitors see old posts or design | Page cache (and the browser's own cache) Admin or settings stay old after a direct DB edit | Object cache A replaced PHP file behaves the same | OPcache Only one external API's result is stale | Transients (see the separate article) The basic method is to **remove one layer at a time.** Check while logged in (which bypasses the page cache), then temporarily disable the persistent object cache, and if nothing changes, suspect OPcache. Clearing everything at once leaves you unsure which layer was the cause. ## The risk of clearing all three at once "Just clear everything" is quick, but sometimes best avoided: * **A full page-cache purge sends the next requests to PHP and the database at once.** In a busy period, load rises briefly. * **Flushing a shared object cache store can affect other sites.** * **Right after an OPcache reset, PHP files are recompiled** , so responses may be briefly slower. Know which layer an action targets, do only what's needed, and do it at a quiet time. ## Summary * The page cache stores finished HTML, the object cache stores values fetched from the database, and OPcache stores PHP code. What they store and how you clear them differ. * The default object cache lasts only within a request. Persisting across requests needs something like Redis plus an `object-cache.php` drop-in. * When a replaced PHP file doesn't take effect, suspect OPcache, and remember `wp cache flush` doesn't clear it. * Narrowing down by symptom and checking one layer at a time works better than clearing everything, both for finding the cause and for managing load. Knowing which caches are active before and after an update makes post-update checks less confusing. The idea of taking a backup before updating is covered in the 3-2-1 rule article.
dev.to
November 17, 2026 at 12:44 AM
PHP muere tras cada petición, y eso es una ventaja: un repaso a cómo ejecuta tu código el motor Zend y por qué no compartir estado evita fugas de memoria. #PHP
PHP Dies After Every Request. How the Zend Engine Actually Runs Your Code.
A visual, 10-minute architectural deep dive into how PHP actually executes under the hood. From the Shared-Nothing process model and OPcache bytecode caching to 16-byte zvals, Copy-on-Write, and the Tracing JIT.
dev.to
November 19, 2026 at 5:00 PM
미디어위키를 운영하다 보면 설정 파일과 문서 곳곳에 캐시라는 말이 나옵니다. OPcache, APCu, memcached, 파서 캐시, 지역화 캐시, 파일 캐시, CDN까지 이름이 많아 어느 것이 무엇을 담는지 헷갈리기 쉽습니다. 미디어위키 위키의 성능 튜닝 문서와 오브젝트 캐시 문서에 대부분 정리되어 있지만, 기본값이 실제로 어떻게 동작하는지나 흔히 빠뜨리는 설정은 코드를 봐야 알 수 있는 부분도 있습니다. 요청 하나가 응답되기까지 쓰이는 캐시를 웹 서버 바깥쪽부터 차례로 정리합니다. 설정 이름과 기본값은 미디어위키 1 […]
Original post on femiwiki.com
femiwiki.com
November 18, 2026 at 4:31 PM
📦 happenv-com/laravel-queue-prefork v1.0.0

Run a pool of Laravel queue workers as forks of one small parent that never loads your app, so every worker shares a single opcache copy of the compiled code.

🔗 https://github.com/happenv-com/laravel-queue-prefork
November 14, 2026 at 2:59 PM
Jamison Bryant uses one CakePHP plugin to scan controllers and build the Swagger JSON, and another to tell OPcache how to prime itself. https://www.phparch.com/podcast/community-corner-podcast-cakephp-with-jamison-bryant/ #PHP #CakePHP #OPcache
November 11, 2026 at 7:05 PM
Build Statamic's Stache 3.3x faster with Flatpack
Build Statamic's Stache 3.3x faster with Flatpack
Compile Statamic's flat-file content at deploy into PHP files OPcache serves from memory. - 1994limited/flatpack-statamic
laravel-news.com
November 10, 2026 at 10:25 PM
📦 1994/flatpack-statamic v1.1.1

Compile Statamic's flat-file content at deploy into PHP files OPcache serves from memory. Content stays in your Markdown and YAML files.

🔗 https://github.com/1994limited/flatpack-statamic
November 10, 2026 at 7:12 PM
📦 tevkert/queue-prefork v1.0.5

Cut the memory of Laravel queue workers by up to 80 %: queue:work and Horizon workers run as forks of one template that shares compiled code through opcache. Drop-in, no code changes.

🔗 https://github.com/tevkert/queue-prefork
November 9, 2026 at 11:59 AM
📦 actra/autoloader v1.2.1

A simple, lightweight, and efficient PHP Autoloader supporting PSR-4, PSR-0, and filesystem caching with OPcache support.

🔗 https://github.com/Actra-AG/autoloader
November 8, 2026 at 5:59 PM
The weekly sweep report of Laravel Snippets crashed. The cause: a bug in PHP's OPcache on 32-bit builds.

I reported it, suggested the fix, and my name is now in php-src 🎉

github.com/php/php-src/...

Now fixed in php-wasm 3.1.62 too 👇
November 2, 2026 at 2:32 PM
Переказали статтю про те, чому воркери черг Laravel займають стільки пам'яті і як queue-prefork зменшив Horizon з 1279 МБ до 240 МБ. https://laravelukraine.com/blog/vorkeri-cerg-laravel-trimaiut-u-pamiati-8-kopii-zastosunku?utm_source=bluesky #Laravel #PHP
Воркери черг Laravel і пам'ять: queue-prefork
Чому воркери queue:work і Horizon займають стільки пам'яті, як порахувати їхній PSS і як queue-prefork зменшив Horizon з 1279 МБ до 240 МБ спільним opcache.
laravelukraine.com
November 2, 2026 at 3:33 PM
PHP OPcache: Faster PHP Without Changing Your Code
#SiteAIAudit #WebsiteAudit #PageSpeed #WebDev

https://getsiteaiaudit.com/php-opcache-performance/
PHP OPcache: Faster PHP Without Changing Your Code #SiteAIAudit #WebsiteAudit #PageSpeed #WebDev
getsiteaiaudit.com
October 31, 2026 at 8:05 AM