Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
From: mengxr <git@git.apache.org>
To: infrastructure-dev@apache.org
Reply-To: infrastructure-dev@apache.org
References: <git-pr-635-incubator-spark@git.apache.org>
In-Reply-To: <git-pr-635-incubator-spark@git.apache.org>
Subject: [GitHub] incubator-spark pull request: SPARK-1122: allCollect
 functions for...
Content-Type: text/plain
Message-Id: <20140225024243.56CBA925583@tyr.zones.apache.org>
Date: Tue, 25 Feb 2014 02:42:43 +0000 (UTC)

Github user mengxr commented on the pull request:

    https://github.com/apache/incubator-spark/pull/635#issuecomment-35969142
  
    @JoshRosen I didn't implement this ... AllCollect is better than directly using broadcast variables if it is implemented without putting heavy load on the driver and data is not very small. But the current implementation is no better than directly broadcasting variables. A slightly better solution would be shuffle-based, which does not put load on the driver but it might create duplicate blocks at the same physical node. The efficient broadcasting you described sounds interesting, but yes I can imagine it is difficult to implement. Thanks for sharing your thoughts!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---