You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by cloud-fan <gi...@git.apache.org> on 2015/10/03 03:05:03 UTC
[GitHub] spark pull request: [SPARK-9066][SQL] Improve cartesian performanc...
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/7417#issuecomment-145190616
@zsxwing the rdds order do matters for `RDD.cartesian`, because of the inefficient way we compute `CartesianRDD`:
```
for (x <- rdd1.iterator(currSplit.s1, context);
y <- rdd2.iterator(currSplit.s2, context)) yield (x, y)
```
For `a.cartesian(b)`, when we compute partition in result RDD, logically we only need to compute the referenced partition of `a` and `b` once, but actually we comput partition of `b` many times according to the number of elements in partition of `a`.
Anyway this PR LGTM
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org