Single process ends up hosting heavy modules #1745
Description
some of our modules are extra GIL heavy - connection for unitree, rerun bridge, those should never be in the same process. some of our modules are extra light and we can host 20 in the same process.
should we fork a single process per module, given linux does copy on write, what is the actual impact on RAM here or optimal strategy for importing py libs pre-fork? investigate
alternatively, and unfortunately, should we tag modules in some way (auto-profile auto-tag even?) so that we can distribute them across processes better?
Synced from DIM-780 by summer