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
Multi-processing should be managed outside of maki-nage in production environment (via the deployment/orchestration tools). However on local usage, it would be useful to support forking in multiple processes instead of requiring the user to launch the application multiple times.
a -j [njobs] option should be added for this. njobs can have several values:
positive indicates the number of workers to spawn
0 means using as many workers as cpus on the system
negative values indicates numbers of cpus minus njobs workers
1 is a special value where no fork is done, and the master process is the single worker. In all other forking configurations, the master process will not act as a worker.
This requires a "fork" cyclotron driver that will be in charge of forking, waiting, and eventually killing the workers from the master (maybe this should be in cyclotron-std).
The text was updated successfully, but these errors were encountered:
Multi-processing should be managed outside of maki-nage in production environment (via the deployment/orchestration tools). However on local usage, it would be useful to support forking in multiple processes instead of requiring the user to launch the application multiple times.
a -j [njobs] option should be added for this. njobs can have several values:
1 is a special value where no fork is done, and the master process is the single worker. In all other forking configurations, the master process will not act as a worker.
This requires a "fork" cyclotron driver that will be in charge of forking, waiting, and eventually killing the workers from the master (maybe this should be in cyclotron-std).
The text was updated successfully, but these errors were encountered: