Does everywhere have a limit on the maximum size of globals?

[olivier7121]

Is there a similar limit as in future on the maximum size of globals (in future it can be set through maxSizeOfObjects and options(future.globals.maxSize = xxx)) that can be exported to daemons?
I looked in the documentation but didn't find anything in that direction.

Just asking because in my particular use case I can successfully use mirai_map after having called everywhere and loaded 3 packages and exported some global variables (these globals amounting to approx. 200 MiB) by setting up up to 4 daemons but from 5 daemons onwards I have issues with some globals that are not found on daemons.
This issue appears when a dispatcher is set when setting up the daemons (default setting).
When setting dispatcher = FALSE it works fine with daemons(5) and daemons(6) ; with daemons(7) I have 5 Unhandled promise error: out-of-bounds index (I indeed added a promise after each mapping inside of mirai_map via .promise).
The computer I'm using has 4 physical cores and 8 logical ones.

[shikokuchuo]

There's no limit on the size of globals. Can you try with the latest dev version to see if this is already solved, e.g.

pak::pak("r-lib/mirai")

If not, the function is likely to be overhauled at some point, so do look out for changelog entries on this.

[olivier7121]

Thank you for your answer!
I tried with versions 2.3.0.9000 and 2.3.0: Unfortunately I still have the same issue.

[shikokuchuo]

I'm closing this discussion as I now have an issue tracking this in #326 (as well as PR #327 which should fix this). Thanks for raising this!