Confirmation about how the worker(s) will process in this async RFC

[macropay-solutions]

Can someone confirm that this RFC falls into first picture from this question: https://langdev.stackexchange.com/questions/4655/is-there-something-better-than-async-in-order-to-avoid-dead-or-unused-processing

The picture is this

[EdmondDantes]

Can someone confirm that this RFC falls into first picture from this question: https://langdev.stackexchange.com/questions/4655/is-there-something-better-than-async-in-order-to-avoid-dead-or-unused-processing

The current implementation works like this:

1. We have a Worker — the waiter.
2. Inside the Worker, there are several coroutines — these are the orders.
3. There is the kitchen, which is the database.

The kitchen is slow and requires time.
Therefore, one waiter (Worker) can handle several orders (requests) at the same time.

Laravel Octane, as far as I know, does not use coroutines. Therefore it doesn’t use all the capabilities that exist.
But perhaps after this RFC it will appear.

[EdmondDantes]

So, it is like I understood it. Only one worker. Thank you.

Yes, and each Worker can have its own coroutines. And together this becomes a very powerful thing :)

[marius-ciclistu]

I hope the gains worth the effort... Maybe the idea behind the Concurrent feature from Laravel that uses background processes would benefit more if it would be perfected.

"Automating" the Fibers' "switch" decision is the only new thing in this RFC because of the single worker.

[marius-ciclistu]

@EdmondDantes
https://www.php.net/manual/en/mysqli.poll.php#128017

mysqli_poll accepting bindings would be a great improvement also.

[marius-ciclistu]

@EdmondDantes I made an update to my question from here. Maybe that path would be easier and with more gains to PHP. Look at pictures 3 and 4. Thank you.

[EdmondDantes]

@EdmondDantes I made an update to my question from here. Maybe that path would be easier and with more gains to PHP. Look at pictures 3 and 4. Thank you.

A model where a single thread handles multiple connections and there is no inter-thread interaction is the most performant scenario for a large number of use cases.