Add an argument store to Future which, if true, stores the value in a distributed object store instead of sending it to the creator PE
Add a garbage collector to delete data from object store when no references to the future are left anywhere in the system
Add a bool is_ray to the message header to differentiate between messages sent to ray actor methods/tasks from messages sent to charm4py method invocations
On the receiving PE, if the message has is_ray=True, the message is buffered until the values of all futures passed as arguments are available locally
The process for linking libcharm.so to the c_object_store library requires a slightly different path than when linking with charmlib_ctypes because charmlib_ctypes is 1 directory level below c_object_store.
Add ray implementation on charm4py
store
toFuture
which, if true, stores the value in a distributed object store instead of sending it to the creator PEis_ray
to the message header to differentiate between messages sent to ray actor methods/tasks from messages sent to charm4py method invocationsis_ray=True
, the message is buffered until the values of all futures passed as arguments are available locally