Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

move to multiprocess from workers #18

Open
amcalabretta opened this issue Oct 19, 2022 · 0 comments
Open

move to multiprocess from workers #18

amcalabretta opened this issue Oct 19, 2022 · 0 comments
Assignees
@amcalabretta
Labels
enhancement New feature or request
Milestone
Move to multiprocess

Comments

@amcalabretta
Copy link
Owner

amcalabretta commented Oct 19, 2022 •
edited
Loading

Multiprocess might be a better way to manage the strategies (especially considering that each strategy might make use of expensive frameworks like ML / AI etc...

see https://betterprogramming.pub/scaling-node-js-applications-with-multiprocessing-b0c25511832a for an example or move to cluster (https://nodejs.org/docs/latest/api/cluster.html#cluster) node native way to run multiple processes rather than threads (i.e. workers)

communication might be done via the pub/sub pattern (https://www.npmjs.com/package/cluster-pubsub)
@amcalabretta amcalabretta added the enhancement New feature or request label Oct 19, 2022
@amcalabretta amcalabretta self-assigned this Oct 19, 2022
@amcalabretta amcalabretta added this to the Move to multiprocess milestone Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amcalabretta amcalabretta

Labels
enhancement New feature or request
Projects
None yet
Milestone
Move to multiprocess
Development

No branches or pull requests
1 participant
@amcalabretta