You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Manoj Kumar (JIRA)" <ji...@apache.org> on 2016/06/14 05:02:57 UTC

[jira] [Commented] (SPARK-14351) Optimize ImpurityAggregator for decision trees

    [ https://issues.apache.org/jira/browse/SPARK-14351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328941#comment-15328941 ] 

Manoj Kumar commented on SPARK-14351:
-------------------------------------

I can try working on this.

> Optimize ImpurityAggregator for decision trees
> ----------------------------------------------
>
>                 Key: SPARK-14351
>                 URL: https://issues.apache.org/jira/browse/SPARK-14351
>             Project: Spark
>          Issue Type: Improvement
>          Components: ML
>            Reporter: Joseph K. Bradley
>
> {{RandomForest.binsToBestSplit}} currently takes a large amount of time.  Based on some quick profiling, I believe a big chunk of this is spent in {{ImpurityAggregator.getCalculator}} (which seems to make unnecessary Array copies) and {{RandomForest.calculateImpurityStats}}.
> This JIRA is for:
> * Doing more profiling to confirm that unnecessary time is being spent in some of these methods.
> * Optimizing the implementation
> * Profiling again to confirm the speedups
> Local profiling for large enough examples should suffice, especially since the optimizations should not need to change the amount of data communicated.



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