You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Zongheng Yang (JIRA)" <ji...@apache.org> on 2014/06/06 02:37:01 UTC
[jira] [Commented] (SPARK-2046) Support config properties that are
changeable across tasks/stages within a job
[ https://issues.apache.org/jira/browse/SPARK-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019457#comment-14019457 ]
Zongheng Yang commented on SPARK-2046:
--------------------------------------
[~shivaram]
> Support config properties that are changeable across tasks/stages within a job
> ------------------------------------------------------------------------------
>
> Key: SPARK-2046
> URL: https://issues.apache.org/jira/browse/SPARK-2046
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Zongheng Yang
>
> Suppose an application consists of multiple stages, where some stages contain computation-intensive tasks, and other stages contain less computation-intensive (or otherwise ordinary) tasks.
> For such job to run efficiently, it might make sense to provide user a function to set "spark.task.cpus" to a high number right before the computation-intensive stages/tasks are getting generated in the user code, and set the property to a lower number for other stages/tasks.
> As a first step, supporting this feature across stages instead of the more fine-grained task-level might suffice.
--
This message was sent by Atlassian JIRA
(v6.2#6252)