[jira] [Resolved] (SPARK-8695) TreeAggregation shouldn't be triggered when it doesn't save wall-clock time

["Sean Owen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-8695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-8695.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

Issue resolved by pull request 7397
[https://github.com/apache/spark/pull/7397]

> TreeAggregation shouldn't be triggered when it doesn't save wall-clock time
> ---------------------------------------------------------------------------
>
>                 Key: SPARK-8695
>                 URL: https://issues.apache.org/jira/browse/SPARK-8695
>             Project: Spark
>          Issue Type: Improvement
>          Components: MLlib, Spark Core
>    Affects Versions: 1.5.0
>            Reporter: Xiangrui Meng
>            Priority: Minor
>              Labels: starter
>             Fix For: 1.5.0
>
>
> If an RDD has 5 partitions, tree aggregation doesn't reduce the wall-clock time. Instead, it introduces scheduling and shuffling overhead. We should update the condition to use tree aggregation (code attached):
> {code}
>       while (numPartitions > scale + numPartitions / scale) {
> {code}



--
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