tustvold commented on issue #13692: URL: https://github.com/apache/datafusion/issues/13692#issuecomment-2527850275
> I can try to take another shot at https://github.com/apache/datafusion/pull/13690 to more fully annotate IO in DataFusion. IMO the key challenge is async is an abstraction designed for IO concurrency, not CPU parallelism. This is what ultimately makes it so difficult to disentangle in a coherent way. Whilst we _can_ dispatch the "IO" off, the boundary inevitably ends up fuzzy, an async task doesn't have a single start and end. I'm increasingly of the opinion that having CPU-bound futures fundamentally breaks their abstraction, and rather than fighting this, DF would be better served by avoiding such things in the first place. Instead if can use async / tokio for what it is designed for, and move the CPU bound work somewhere else. I don't actually think this would be that bad, most kernels are synchronous and could be offloaded without too much ceremony. It would also be largely mechanical, and something that could easily be actioned by a broad contributor base. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
