You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As presently constituted, the asyncify package relies primarily on child processes spawnable by the kernel. Though safe and sequestered from the userspace, child processes can be quite bulky for they are effectively duplicates of the runtime. Multithreading offers parallelism siloed to a single process, and when implemented per the rules of Communicating Sequential Processes (CSP), can allow for the sharing of state among atomic work units (threads). Currently, CSP is accessible in PHP via ext-parallel, and is primed for interoperability with ReactPHP by the suite of packages in reactphp-parallel the most recent release in which also offers the cooperative multitasking in the fiber spec.
The goal here is to instate multithreading in reactphp-parallel as the default mechanism for running blocking code in PHP in a non-blocking fashion with asyncify while retaining the child process approach as a fallback strategy.
The text was updated successfully, but these errors were encountered:
As presently constituted, the asyncify package relies primarily on child processes spawnable by the kernel. Though safe and sequestered from the userspace, child processes can be quite bulky for they are effectively duplicates of the runtime. Multithreading offers parallelism siloed to a single process, and when implemented per the rules of Communicating Sequential Processes (CSP), can allow for the sharing of state among atomic work units (threads). Currently, CSP is accessible in PHP via
ext-parallel
, and is primed for interoperability with ReactPHP by the suite of packages inreactphp-parallel
the most recent release in which also offers the cooperative multitasking in the fiber spec.The goal here is to instate multithreading in
reactphp-parallel
as the default mechanism for running blocking code in PHP in a non-blocking fashion withasyncify
while retaining the child process approach as a fallback strategy.The text was updated successfully, but these errors were encountered: