alamb commented on PR #14286: URL: https://github.com/apache/datafusion/pull/14286#issuecomment-2619967575
> It seems to me like most folks agree research into schedulers for the CPU work that can sit within the single tokio runtime would be _much_ easier to integrate for downstream use cases, probably at the cost of complexity (overheads?) within datafusion itself. @davidhewitt I agree in principle. I think any time one has to cross from sync code to async code the API is going to get challenging. The upside of the current DataFusion approach with a single tokio runtime is it just "works" (for some defintion of work) The downside is that squeezing out the maximum performance is tough -- 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
