GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/2933
use broadcast for task only when task is large enough
Using broadcast for small tasks has no benefits or even some regressions
(several RPCs), also there some stable issues with broadcast, so we should use
broadcast for tasks only when the serialized tasks are large enough (larger
than 8k, be default, maybe changed in future).
In practice, most of tasks are small, so this should improve the stability
for most user cases, especially for tests, which will start and stop context
multiple times.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davies/spark broadcast
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/2933.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2933
----
commit 4ca3caa3f56e56139b2e33151ff95688232c4fe3
Author: Davies Liu <dav...@databricks.com>
Date: 2014-10-24T20:22:58Z
use broadcast when task is large enough
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
