You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiangrui Meng (JIRA)" <ji...@apache.org> on 2015/04/28 03:06:07 UTC
[jira] [Updated] (SPARK-5842) Allow creating broadcast variables on
workers
[ https://issues.apache.org/jira/browse/SPARK-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiangrui Meng updated SPARK-5842:
---------------------------------
Target Version/s: (was: 1.4.0)
> Allow creating broadcast variables on workers
> ---------------------------------------------
>
> Key: SPARK-5842
> URL: https://issues.apache.org/jira/browse/SPARK-5842
> Project: Spark
> Issue Type: New Feature
> Components: MLlib, Spark Core
> Reporter: Xiangrui Meng
>
> Now broadcast variables must be created by the driver. Many algorithms in MLlib uses the driver to collect gradient and broadcast the new weights, which makes driver a bottleneck. It would be nice if we can create broadcast variables on workers and return their handlers to the driver. An ML iteration will look like the following after this change:
> (training data + broadcasted weights) ->reduceByKey -> single partition RDD with aggregated gradient -> update weights and broadcast it -> driver receives the broadcast variable
> where the driver is only doing the scheduling work.
--
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