I’m interested in using/extending glow to run multiple networks concurrently. From what I found out so far, the compilation process for some network works as follows:
- A caffe2 or onnx network is loaded into one glow::function inside a glow:module
- This module can be added to the HostManager where the compilation, optimizations and partitioning happen
Therefor, when multiple networks are added, the DAGs of the single networks are created independantly from each other, right? If that is correct, do the overall physically available resources need to be partitioned in advance for the networks?
What I want to achieve is to do the partitioning, taking all the loaded networks into account. Is that something that should even be supported by glow sooner or later, or is that not desired?
Maybe the most simple solution, concerning the current situation would be to just load multiple networks into one module, but that seems a bit hacky to me?