Every stream arrives at once. The CPU takes them one at a time.
- Longer reaction time — every result waits on four memory trips
- Delay that varies frame to frame — each stream waits its turn on the CPU
- Adding a sensor degrades latency for all of them
Every sensor produces a raw stream, and every stream is hauled to a processor before anything useful happens to it. In sensor-dense systems that movement, not the computation, is becoming the bottleneck — and sensor counts are still climbing.
Every one of those numbers is still rising, and each sensor adds a stream.
In sensing-intensive systems every raw stream is written to shared memory, pre-processed by the CPU, written back, and only then read by the accelerator. RiDM does that work where the data is produced.
Illustrative data path
DODA runs an operation when its data is ready, rather than following a schedule fixed when the program was compiled. The pipeline can be rebuilt for a new workload without new silicon.
Dynamically Orchestrated Dataflow Architecture
Orchestration happens as data arrives, not ahead of time. That is the difference between a dataflow machine and a fixed pipeline.
Jinho Lee’s PhD research at NUS, pursuing a general-purpose dataflow architecture that is both fast and efficient.
NUS ScholarBank ↗Covering the core architecture, its interconnect, and runtime reconfiguration.