Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126544
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com>
 <c1b1295e-a4c7-434f-8881-2d01a790fd83@rwec.co.uk> <c0db0315-e99f-4441-bcc3-dc5867d27542@app.fastmail.com>
In-Reply-To: <c0db0315-e99f-4441-bcc3-dc5867d27542@app.fastmail.com>
Date: Sat, 1 Mar 2025 21:33:14 +0200
Message-ID: <CAMW7n8Ck5uS+kVO3f=2ZW8GHNAYaKY=8Q7LzaZ0+svrRqJZA8g@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
To: Rob Landers <rob@bottled.codes>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000002c3cad062f4cff8e"
From: edmond.ht@gmail.com (Edmond Dantes)

--0000000000002c3cad062f4cff8e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> but it would be interesting to replace the scheduler with something that
> utilized go-routines for true multi-threading. Whether that works or not,
> is a whole different can of worms.
>
> =E2=80=94 Rob
>
If the question is whether it is possible to interact with a PHP thread
from another thread by sending an event to the Reactor, the answer is yes,
it is possible. Moreover, from the PHP-land side, this could be a Channel.

If the question is deeper =E2=80=94 replacing the Scheduler with a Schedule=
r in
another language or from a different ecosystem =E2=80=94 then it is more li=
kely
possible than not, considering that the module itself is separated from the
rest of the implementation.
If you know a situation where this would be useful, then why not.

For example, in cases of integration with a web server, we can just send a
message through a channel from "server-thread" to "php-thread", and in a
microtask written in C, for example, create Fibers to handle the request.
This approach is used in Swoole.

And this solution should be even slightly faster than in Swoole because the
interaction will occur through memory copying within a single process.

If memory copying is to be avoided, then the web server can be integrated
directly into the Reactor, making the web server itself run as a microtask.
Since the memory will be allocated immediately in the correct thread, there
won=E2=80=99t even be a need to copy it, which in some cases might provide =
a
performance boost. Or maybe not...

Ed.

--0000000000002c3cad062f4cff8e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote gmail=
_quote_container"><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 cl=
ass=3D"msg3984106583317614379"><div>but it would be interesting to replace =
the scheduler with something that utilized go-routines for true multi-threa=
ding. Whether that works or not, is a whole different can of worms.</div><d=
iv><br></div><div id=3D"m_3984106583317614379sig121229152">=E2=80=94 Rob<br=
></div></div></blockquote><div>

If the question is whether it is possible to interact with a PHP thread fro=
m another thread by sending an event to the Reactor, the answer is yes, it =
is possible. Moreover, from the PHP-land side, this could be a Channel.</di=
v><div><br></div><div>

If the question is deeper =E2=80=94 replacing the Scheduler with a Schedule=
r in another language or from a different ecosystem =E2=80=94 then it is mo=
re likely possible than not, considering that the module itself is separate=
d from the rest of the implementation.

=C2=A0</div><div>If you know a situation where this would be useful, then w=
hy not.</div><div><p>For example, in cases of integration with a web server=
, we can just send a message through a channel from &quot;server-thread&quo=
t; to &quot;php-thread&quot;, and in a microtask written in C, for example,=
 create Fibers to handle the request. This approach is used in Swoole.</p><=
p>And this solution should be even slightly faster than in Swoole because t=
he interaction will occur through memory copying within a single process.</=
p><p>If memory copying is to be avoided, then the web server can be integra=
ted directly into the Reactor, making the web server itself run as a microt=
ask. Since the memory will be allocated immediately in the correct thread, =
there won=E2=80=99t even be a need to copy it, which in some cases might pr=
ovide a performance boost. Or maybe not...</p><p>Ed.</p></div></div></div>

--0000000000002c3cad062f4cff8e--