Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129727
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F62A7661-B790-462A-A42E-186E1AD21140"
Precedence: list
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: [PHP-DEV] [Discussion] Reflection-based constructor autowiring
 (scope clarification)
Date: Wed, 31 Dec 2025 01:23:27 +0200
References: <C537E26A-9088-4507-8468-FCCE534A5906@gmail.com>
 <CADyq6sK8-FqvoPtqQzQO0o9GYj_u8gXnRwTeTu+oZwwVnkd4rA@mail.gmail.com>
 <6C2A8D96-BB4C-4091-85D8-21654C242364@gmail.com>
 <CADyq6sLrbzb19cRBA-rSrXb-LQ8o0u=tsRLuEyoh4nQjzT14uA@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
In-Reply-To: <CADyq6sLrbzb19cRBA-rSrXb-LQ8o0u=tsRLuEyoh4nQjzT14uA@mail.gmail.com>
Message-ID: <9BB22BFE-CB1B-4A25-A911-8181B76B0613@gmail.com>
From: azolee@gmail.com (=?utf-8?B?QU5EUsOBUyBab2x0w6FuIEd5w6FyZsOhcw==?=)


--Apple-Mail=_F62A7661-B790-462A-A42E-186E1AD21140
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi all,

I=E2=80=99ve completed the benchmarks based on the guidance in the =
thread.

In short:

Cold-start measurements (fresh PHP process per run) show no meaningful =
difference between direct instantiation and reflection-based autowiring. =
Process startup dominates, and reflection overhead is effectively lost =
in the noise.
Warm-process benchmarks show a consistent ~3-4x overhead for runtime =
autowiring compared to direct instantiation, even with request-scope =
constructor plan caching. This appears to be a model-level cost rather =
than something easily eliminated by implementation details alone.

Based on these results, I don=E2=80=99t see a lazy-proxy-like =
engine-only win here. Userland implementations already seem close to the =
practical ceiling for runtime autowiring, and further gains would likely =
be incremental.

Given that, I agree this does not currently make a compelling case for a =
core addition, and that runtime autowiring remains better addressed in =
userland or framework-specific solutions.

Thanks to everyone who provided feedback and guidance.

Best regards,

Zoli



eng. ANDR=C3=81S Zolt=C3=A1n-Gy=C3=A1rf=C3=A1s
---------------------------------------
tel: +40 745 797 798
mail: azolee@gmail.com

> On 30 Dec 2025, at 20:41, Marco Pivetta <ocramius@gmail.com> wrote:
>=20
> Hey Zoli,
>=20
> On Tue, 30 Dec 2025 at 08:17, ANDR=C3=81S Zolt=C3=A1n Gy=C3=A1rf=C3=A1s =
<azolee@gmail.com <mailto:azolee@gmail.com>> wrote:
>> If you have any guidance on what you would consider a representative =
benchmark or a meaningful performance threshold for =E2=80=9Cworth =
moving into core=E2=80=9D, I=E2=80=99d appreciate it.
>>=20
>=20
> In the grand majority of cases where autowiring is meaningful (at =
least for PHP), you care about a "cold start" of the application =
(although that's changing with ReactPHP/FrankenPHP/Roadrunner/etc.).
>=20
> You may design a PHPBench or Hyperfine test that:
>=20
> * starts a PHP process, autowires something, shuts down. Hyperfine =
helps a lot here.
> * repeats the above, but within a warm process (classes already =
loaded, tight loop repeating the operation). PHPBench is a bit more =
precise here.
>=20
> You probably care about these cases:
>=20
> * zero-arguments constructor
> * simple concrete class references
> * default constructor arguments
> * resolvers
> * autowiring of a complex multi-level structure
>=20
> In all the above cases, you probably care about the usage with =
autowiring API vs the usage via direct instantiation, so you can see the =
exact overhead.
>=20
> Marco Pivetta=20
>=20
> https://mastodon.social/@ocramius
>=20
> https://ocramius.github.io/
> =20


--Apple-Mail=_F62A7661-B790-462A-A42E-186E1AD21140
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><div><p =
class=3D"isSelectedEnd">Hi all,</p><p class=3D"isSelectedEnd">I=E2=80=99ve=
 completed the benchmarks based on the guidance in the thread.</p><p =
class=3D"isSelectedEnd">In short:</p><p class=3D"isSelectedEnd"><ul =
class=3D"MailOutline"><li>Cold-start measurements (fresh PHP process per =
run) show no meaningful difference between direct instantiation and =
reflection-based autowiring. Process startup dominates, and reflection =
overhead is effectively lost in the noise.</li><li>Warm-process =
benchmarks show a consistent ~3-4x overhead for runtime autowiring =
compared to direct instantiation, even with request-scope constructor =
plan caching. This appears to be a model-level cost rather than =
something easily eliminated by implementation details =
alone.</li></ul></p><p class=3D"isSelectedEnd">Based on these results, I =
don=E2=80=99t see a lazy-proxy-like engine-only win here. Userland =
implementations already seem close to the practical ceiling for runtime =
autowiring, and further gains would likely be incremental.</p><p =
class=3D"isSelectedEnd">Given that, I agree this does not currently make =
a compelling case for a core addition, and that runtime autowiring =
remains better addressed in userland or framework-specific =
solutions.</p><p class=3D"isSelectedEnd">Thanks to everyone who provided =
feedback and guidance.</p><p>Best =
regards,</p></div><div>Zoli</div><div><br></div><div><br></div><br =
id=3D"lineBreakAtBeginningOfMessage"><div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;">eng. ANDR=C3=81S =
Zolt=C3=A1n-Gy=C3=A1rf=C3=A1s<br>---------------------------------------<b=
r>tel: +40 745 797 798<br>mail:&nbsp;azolee@gmail.com</div>
</div>
<div><br><blockquote type=3D"cite"><div>On 30 Dec 2025, at 20:41, Marco =
Pivetta &lt;ocramius@gmail.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div dir=3D"ltr"><div =
dir=3D"ltr"><div>Hey Zoli,</div></div><br><div class=3D"gmail_quote =
gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, 30 =
Dec 2025 at 08:17, ANDR=C3=81S Zolt=C3=A1n Gy=C3=A1rf=C3=A1s &lt;<a =
href=3D"mailto:azolee@gmail.com">azolee@gmail.com</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div><p>If you have any guidance on =
what you would consider a representative benchmark or a meaningful =
performance threshold for =E2=80=9Cworth moving into core=E2=80=9D, =
I=E2=80=99d appreciate it.</p></div></blockquote><div><br></div><div>In =
the grand majority of cases where autowiring is meaningful (at least for =
PHP), you care about a "cold start" of the application (although that's =
changing with =
ReactPHP/FrankenPHP/Roadrunner/etc.).</div><div><br></div><div>You may =
design a PHPBench or Hyperfine test that:</div><div><br></div><div>* =
starts a PHP process, autowires something, shuts down. Hyperfine helps a =
lot here.</div><div>* repeats the above, but within a warm process =
(classes already loaded, tight loop repeating the operation). PHPBench =
is a bit more precise here.</div><div><br></div><div>You probably care =
about these cases:</div><div><br></div><div>* zero-arguments =
constructor</div><div>* simple concrete class references</div><div>* =
default constructor arguments</div><div>* resolvers</div><div>* =
autowiring of a complex multi-level =
structure</div><div><br></div><div>In all the above cases, you probably =
care about the usage with autowiring API vs the usage via direct =
instantiation, so you can see the exact =
overhead.</div><div><br></div><div><div></div><div><div dir=3D"ltr" =
class=3D"gmail_signature"><div dir=3D"ltr">Marco Pivetta <br><br><a =
href=3D"https://mastodon.social/@ocramius" =
target=3D"_blank">https://mastodon.social/@ocramius</a><br><br><a =
href=3D"https://ocramius.github.io/" =
target=3D"_blank">https://ocramius.github.io/</a></div></div></div>&nbsp;<=
/div></div></div>
</div></blockquote></div><br></body></html>=

--Apple-Mail=_F62A7661-B790-462A-A42E-186E1AD21140--