I didn't quite get it from the initial skim of this page. But here's the key bit: > [existing solutions slow] ... due to extensive data movement across the fu

I didn't quite get it from the initial skim of this page. But here's the key bit: > [existing solutions slow] ... due to extensive data movement across the functions. Weld’s take on solving this problem is to lazily build up a computation for the entire workflow, optimizing and evaluating it only when a result is needed. The "Background" [1] section of the tutorial has more info too. I've done lots of optimizations before with CPU/GPU computations and I've definitely noticed that minimizing trips across the bus and doing computation during bus activity is critical to saturating the processors/memory. But would we see the orders-of-magnitude improvements shown on this page for CPU-only work? I can't quite tell what was measured in the graphs. [1] https://github.com/weld-project/weld/blob/master/docs/tutorial.md#weld-background https://github.com/weld-project/weld/blob/master/docs/tutori...