Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130912
Precedence: list
MIME-Version: 1.0
Date: Sun, 17 May 2026 00:19:31 +0900
Message-ID: <CABTDVhBhT5OVGfMV7eZZs6Ysuu0ggcDYkmUHP6v1eTnVdwD6tQ@mail.gmail.com>
Subject: [PHP-DEV] [RFC] [Discussion] OPcache Static Cache
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004fc53b0651f0ddeb"
From: zeriyoshi@gmail.com (Go Kudo)

--0000000000004fc53b0651f0ddeb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi internals,

I'd like to start the discussion for a new RFC, OPcache Static Cache.

RFC: https://wiki.php.net/rfc/opcache_static_cache
Implementation: https://github.com/php/php-src/pull/22052

The proposal adds an OPcache-managed shared-memory cache for explicit
userland values and for selected PHP static state. It introduces explicit
functions under the OPcache namespace (volatile_* and persistent_*) and two
attributes, #[OPcache\VolatileStatic] and #[OPcache\PersistentStatic], that
let selected static properties and method static variables survive across
requests. The feature is disabled by default and only activates once memory
is allocated through the new INI directives.

The RFC covers the motivation, the deliberate split between the two
backends, the trust model (one PHP runtime =3D one trust domain; this is no=
t
a tenant isolation boundary), and benchmarks against APCu on NTS php-fpm
and ZTS FrankenPHP. The PR is the full implementation, with PHPT coverage
summarized in the Validation section.

One thing to flag on the implementation status: the Windows build is
currently broken. I don't have a Windows development environment available
yet =E2=80=94 one is being arranged through work, and I'll get the Windows =
side
fixed once that's in place.

Feedback welcome.

Best Regards,
Go Kudo

--0000000000004fc53b0651f0ddeb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi internals,<br><br>I&#39;d like to star=
t the discussion for a new RFC, OPcache Static Cache.<br><br>RFC: <a href=
=3D"https://wiki.php.net/rfc/opcache_static_cache">https://wiki.php.net/rfc=
/opcache_static_cache</a><br>Implementation: <a href=3D"https://github.com/=
php/php-src/pull/22052">https://github.com/php/php-src/pull/22052</a><br><b=
r>The proposal adds an OPcache-managed shared-memory cache for explicit use=
rland values and for selected PHP static state. It introduces explicit func=
tions under the OPcache namespace (volatile_* and persistent_*) and two att=
ributes, #[OPcache\VolatileStatic] and #[OPcache\PersistentStatic], that le=
t selected static properties and method static variables survive across req=
uests. The feature is disabled by default and only activates once memory is=
 allocated through the new INI directives.<br><br>The RFC covers the motiva=
tion, the deliberate split between the two backends, the trust model (one P=
HP runtime =3D one trust domain; this is not a tenant isolation boundary), =
and benchmarks against APCu on NTS php-fpm and ZTS FrankenPHP. The PR is th=
e full implementation, with PHPT coverage summarized in the Validation sect=
ion.<br><br>One thing to flag on the implementation status: the Windows bui=
ld is currently broken. I don&#39;t have a Windows development environment =
available yet =E2=80=94 one is being arranged through work, and I&#39;ll ge=
t the Windows side fixed once that&#39;s in place.<br><br>Feedback welcome.=
<br><br>Best Regards,<br>Go Kudo</div>
</div>

--0000000000004fc53b0651f0ddeb--