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
{{ message }}
This repository has been archived by the owner on Jul 15, 2022. It is now read-only.
There is a new worker multi-threading feature that is in experimental stage. Do you want to explore changing the child process spawn into multi-threaded architecture for the package instead of multi-process architecture. I would love to collaborate if you want. I am sure it will be more performant. Right now, applications like drupal work with the package. But it gives a choppy feeling due to the lag/cost of spawning and getting the result. The process is basically getting the entire result and once received it sends the data - performance hit. It is spawning a child process for every request also which will move into a performance issue soon - second performance hit.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There is a new worker multi-threading feature that is in experimental stage. Do you want to explore changing the child process spawn into multi-threaded architecture for the package instead of multi-process architecture. I would love to collaborate if you want. I am sure it will be more performant. Right now, applications like drupal work with the package. But it gives a choppy feeling due to the lag/cost of spawning and getting the result. The process is basically getting the entire result and once received it sends the data - performance hit. It is spawning a child process for every request also which will move into a performance issue soon - second performance hit.
The text was updated successfully, but these errors were encountered: