pan3793 commented on PR #57332: URL: https://github.com/apache/spark/pull/57332#issuecomment-5004974446
cc @HyukjinKwon, as you also raised the same idea in https://github.com/apache/spark/pull/40730#issuecomment-1506142915 > I have been wondering if it's better to allow `spark.task.cpus` to set a floating number like 0.2 so I/O intensive tasks can benefit from that as well as the case like this. background: we do have observed a large set of such I/O-bound workloads on our cluster, which take a few CPU time but occupy many executor core slots cc @dongjoon-hyun @sunchao @mridulm @tgravescs @wangyum for review, thank you in advance -- 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]
