Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129223
Precedence: list
MIME-Version: 1.0
Date: Fri, 14 Nov 2025 10:49:14 +0100
Message-ID: <CANSNCr2JXXmLnNqSxVXQM7i3j_WBi3jmznM4-_rd34LDkmvLZg@mail.gmail.com>
Subject: [PHP-DEV] What's the status of the JIT?
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000becd2806438ae9a6"
From: brent.roose@jetbrains.com (Brent Roose)

--000000000000becd2806438ae9a6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi internals

I'm wondering about the state of PHP's JIT these days. I understand that
Dmitry is still working on his standalone JIT IR framework [1] that's being
used by PHP, and that Arnaud is maintaining it from the Foundation/PHP
side? In my own benchmarks, done in PHP 8.0 and PHP 8.4; I cannot seem to
get any meaningful performance gain from the JIT in web applications or in
tools like PHPStan. [2][3][4]

The question I'm left with is whether the JIT is worth the hassle? Assuming
the JIT's existence impacts the complexity of internal development, I
wonder if it wouldn't be better to deprecate it in a future PHP version? To
be clear, I'm assuming the JIT impacts internal development =E2=80=94 maybe=
 that's
wrong? Perhaps I'm missing a real-life use case that benefits significantly
from the JIT as well?

Kind regards
Brent

[1] https://github.com/dstogov/ir
[2] https://stitcher.io/blog/jit-in-real-life-web-applications
[3] https://youtu.be/2Njl1ZiCXIk?si=3DqytMIVxt0oTC3b1F&t=3D1057
[4] https://www.youtube.com/watch?v=3D5ResKrAnpBw

--000000000000becd2806438ae9a6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi internals<div><br></div><div>I&#39;m w=
ondering about the state of PHP&#39;s JIT these days. I understand that Dmi=
try is still working on his standalone JIT IR framework [1] that&#39;s bein=
g used by PHP, and that Arnaud is maintaining it from the Foundation/PHP si=
de? In my own benchmarks, done in PHP 8.0 and PHP 8.4; I cannot seem to get=
 any meaningful performance gain from the JIT in web applications or in too=
ls like PHPStan.=C2=A0[2][3][4]</div><div><br></div><div>The question I&#39=
;m left with is whether the JIT is worth the hassle? Assuming the JIT&#39;s=
 existence impacts the complexity of internal development, I wonder if it w=
ouldn&#39;t be better to deprecate it in a future PHP version? To be clear,=
 I&#39;m assuming the JIT impacts internal development =E2=80=94 maybe that=
&#39;s wrong? Perhaps I&#39;m missing a real-life use case that benefits si=
gnificantly from the JIT as well?</div><div><br></div><div>Kind regards</di=
v><div>Brent</div><div><br></div><div>[1]=C2=A0<a href=3D"https://github.co=
m/dstogov/ir" target=3D"_blank">https://github.com/dstogov/ir</a></div><div=
>[2]=C2=A0<a href=3D"https://stitcher.io/blog/jit-in-real-life-web-applicat=
ions" target=3D"_blank">https://stitcher.io/blog/jit-in-real-life-web-appli=
cations</a></div><div>[3]=C2=A0<a href=3D"https://youtu.be/2Njl1ZiCXIk?si=
=3DqytMIVxt0oTC3b1F&amp;t=3D1057" target=3D"_blank">https://youtu.be/2Njl1Z=
iCXIk?si=3DqytMIVxt0oTC3b1F&amp;t=3D1057</a></div><div>[4]=C2=A0<a href=3D"=
https://www.youtube.com/watch?v=3D5ResKrAnpBw" target=3D"_blank">https://ww=
w.youtube.com/watch?v=3D5ResKrAnpBw</a></div></div>
</div>

--000000000000becd2806438ae9a6--