Replies: 3 comments 1 reply
-
Thanks for the feedback. Everything in futureverse uses multi_processing_. That's actually the only way you can parallelize R code. Multi_threading_ is not supported - to use multi_threading_ one has to implement it in C, C++, ..., which is a whole different game and basically outside of R. The R option I'll see if I can clarify this in the documentation. If you have suggestions on where in the docs to make it clear that the futureverse is dealing with multiprocessing and not multithreading, please let me know. |
Beta Was this translation helpful? Give feedback.
-
:O Thx!, now is a lot more clear, to me is sad we can't use multithreading, would helps for some process...... Thx! |
Beta Was this translation helpful? Give feedback.
-
after thinking about this, maybe would be useful the next things:
That should clarify and avoid confusion in the future. Thx! |
Beta Was this translation helpful? Give feedback.
-
Hi hi, I'm little confused about this, is like there is mixed doc.
Lets say the basic difference, multithreading shares the memory with the main process, so we can edit variables in the main process, while in multiprocess, every function is executed in a isolated process, so we can't edit the vars in the main session, but we can use the available copy in the child process to work with them.
Actually the plans to use in future talk about childs in r sessions, so is probable a multiprocess, while in
https://rdrr.io/cran/future/man/future.options.html
We can see an option,
future.fork.multithreading.enable
that talks about multithreading, so..., I'm not sure...I think would be great have a place in the doc to tell us, how to use mulithreading, and how to use multiprocess.
Thx!.
Beta Was this translation helpful? Give feedback.
All reactions