You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2015/05/06 18:45:59 UTC

[jira] [Commented] (SPARK-664) Accumulator updates should get locally merged before sent to the driver

    [ https://issues.apache.org/jira/browse/SPARK-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530859#comment-14530859 ] 

Reynold Xin commented on SPARK-664:
-----------------------------------

I'm going to close this due to inactivity. Also unclear because based on PRs submitted in the past we are going towards the direction of lower latency rather than higher throughput.

> Accumulator updates should get locally merged before sent to the driver
> -----------------------------------------------------------------------
>
>                 Key: SPARK-664
>                 URL: https://issues.apache.org/jira/browse/SPARK-664
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Imran Rashid
>            Priority: Minor
>
> Whenever a task finishes, the accumulator updates from that task are immediately sent back to the driver.  When the accumulator updates are big, this is inefficient because (a) a lot more data has to be sent to the driver and (b) the driver has to do all the work of merging the updates together.
> Probably doesn't matter for small accumulators / low number of tasks, but if both are big, this could be a big bottleneck.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org