zuston commented on issue #2572: URL: https://github.com/apache/datafusion-comet/issues/2572#issuecomment-3404199030
> Yeah I suspect this is fairly over-subscribing on threads. This might actually make sense for I/O heavy workloads with a lot of parallel requests (if we can manage to submit all of that), but it's definitely a good point of discussion. According to Tokio best practices, heavy I/O workloads should be delegated to the Tokio blocking thread pool. > In some environments, such as Kubernetes, the number of spark executor cores and number of "physical" cores in the container would typically be the same. In the Hadoop YARN environment, this behavior is inconsistent with how it runs on Kubernetes. Maybe the default number of Tokio worker threads should be aligned with the number of Spark executor cores. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
