When wrapping cuPyNumeric (and legate code in general) in interactive Apps (streamlit) or APIs (FastAPI) cuPyNumeric code will get executed in different order, when clicking in the app or making a request.
This works fine in Single-Node but for Multi-Node the execution of the code will diverge and creates issues.
We should support this scenario. with either a client-server architecture or also safe single node execution that allows one rank to trigger compute in others?
When wrapping cuPyNumeric (and legate code in general) in interactive Apps (streamlit) or APIs (FastAPI) cuPyNumeric code will get executed in different order, when clicking in the app or making a request.
This works fine in Single-Node but for Multi-Node the execution of the code will diverge and creates issues.
We should support this scenario. with either a client-server architecture or also safe single node execution that allows one rank to trigger compute in others?