You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:15:41 UTC

[jira] [Resolved] (SPARK-3383) DecisionTree aggregate size could be smaller

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

Hyukjin Kwon resolved SPARK-3383.
---------------------------------
    Resolution: Incomplete

> DecisionTree aggregate size could be smaller
> --------------------------------------------
>
>                 Key: SPARK-3383
>                 URL: https://issues.apache.org/jira/browse/SPARK-3383
>             Project: Spark
>          Issue Type: Improvement
>          Components: MLlib
>    Affects Versions: 1.1.0
>            Reporter: Joseph K. Bradley
>            Priority: Minor
>              Labels: bulk-closed
>
> Storage and communication optimization:
> DecisionTree aggregate statistics could store less data (described below).  The savings would be significant for datasets with many low-arity categorical features (binary features, or unordered categorical features).  Savings would be negligible for continuous features.
> DecisionTree stores a vector sufficient statistics for each (node, feature, bin).  We could store 1 fewer bin per (node, feature): For a given (node, feature), if we store these vectors for all but the last bin, and also store the total statistics for each node, then we could compute the statistics for the last bin.  For binary and unordered categorical features, this would cut in half the number of bins to store and communicate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org