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 }}
Repository navigation
[Feature] Support for running jobs in child processes #488
Many times, processes are long and synchronous. Currently design does not allow to run these kind of processes properly due to the locking mechanism. However, we can spawn a child process where the job is run instead. If the same child process is reused for every job (and we will need as many child processes as concurrency levels), the overhead will be minimum. Also as an added benefit, if the child process dies for any reason (memory leaks, or other cause), the worker will still be able to spawn a child replacement and continue working normally.
Reacted by Brad Vogel, Adam Dunkley, Andrew Grathwohl, Georgios Foteinopoulos, bogini, Tin Nguyen, shanzemin, Gilles Yvetot, Hieu Dang, Raghav Garg and 20 more
Reacted by carcinocron, Brad Vogel, Andrew Grathwohl, Tin Nguyen, shanzemin, Sasha Marrocco, Stanley Lara, Myung-gwan Kim and 윤종하
Reacted by Ramin Mo, Ferron H, Brad Vogel, Andrew Grathwohl, Karthik Iyengar, Tin Nguyen, Raghav Garg, Sasha Marrocco, Bruno Alexandre and Stanley Lara
Activity
Change default lock timeout to 30sec. It's a more sensible default fo…
docs: add a hyperlink to #488 in README
docs: add a hyperlink to OptimalBits#488 in README