You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2017/12/25 06:59:00 UTC

[jira] [Resolved] (SPARK-22707) Optimize CrossValidator memory occupation by models in fitting

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

Joseph K. Bradley resolved SPARK-22707.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

Resolved by https://github.com/apache/spark/pull/19904

> Optimize CrossValidator memory occupation by models in fitting
> --------------------------------------------------------------
>
>                 Key: SPARK-22707
>                 URL: https://issues.apache.org/jira/browse/SPARK-22707
>             Project: Spark
>          Issue Type: Improvement
>          Components: ML
>    Affects Versions: 2.2.0
>            Reporter: Weichen Xu
>            Assignee: Weichen Xu
>             Fix For: 2.3.0
>
>
> Via some test I found CrossValidator still exists memory issue, it will still occupy `O(n*sizeof(model))` for holding models when fitting, if well optimized, it should be `O(parallelism*sizeof(model))`
> This is because modelFutures will hold the reference to model object after future is complete (we can use `future.value.get.get` to fetch it), and the `Future.sequence` and the `modelFutures` array holds references to each model future. So all model object are keep referenced. So it will still occupy `O(n*sizeof(model))` memory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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