ooh, forgot to mention...there's also a fully distributed setup that's coming soon (well, already here...removed b/c I'm re-coding it). The original multi-node

ooh, forgot to mention...there's also a fully distributed setup that's coming soon (well, already here...removed b/c I'm re-coding it). The original multi-node (UDP) stack came from a summer research student. It functioned, but not that well. Since I'm spending time optimizing that, I'm also adding container support so remote kernels will operated inside a container w/a common file system view. Another difference I probably didn't mention is that there is an instrumentation package that monitors the actual non-blocking service rate in real time (well, as real time as you can be across multiple clocking domains). The acyclic graph structure is awesome for using things like non-blocking service rate to optimize placement, make parallelization choices, etc. My original interest was using this framework for my online optimization work. Basically I've been using support vector machines and neural networks to select models and make buffer sizing decisions....