Do multisession and multicore futures work on Apple Silicon (natively or in emulation)? #463
-
My Late 2013 15" MBP is rapidly giving up the ghost, and I am keen to move into some new hardware digs. Given that native R on Apple Silicon is not fully baked (as discussed here), I'm left with the option of running R in emulation (Rosetta 2) on a new M1 13" MBP, moving to a Linux rig, or just living in the cloud. (A fourth option to drop$3K+ on an Intel 16" MBP doesn't seem to be a wise choice when Apple will be EOLing them this year--or perhaps R will shun ARM architectures so get an Intel rig while I can?) To better inform a decision, does anyone know if To be sure, futures running on Apple Silicon via emulation is not the only issue (there are many more), but any insights w/r to Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I don't own Apple equipments but this is what I can say:
|
Beta Was this translation helpful? Give feedback.
I don't own Apple equipments but this is what I can say:
multisession
workers are just regular R sessions running in the background and taking commands over socket connection. Except for being set up via the parallelly package, they're basicallyparallel::makePSOCKcluster()
workers. Because of this, I'd be extremely surprised if this would not work. I expect them to work on all OSes and architectures where R runs.multicore
workers rely on forked parallel processing and use theparallel::mclapply()
framework internally. Forked processing is quite low level and probably requires getting libraries and compilers correct. So, it might be that those will be unstable for a while until thoro…