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

Peng Meng edited comment on SPARK-21476 at 7/25/17 6:55 AM:
------------------------------------------------------------

Hi @Suarabh, I am profiling RF transform performance. I change transform to use 
transformImpl which uses broadcast, but find there is no performance 
improvement. 
Could you show me what is your case?  For example, the tree size, number of 
features, dataset partitions, and number of executors. Thanks. 


was (Author: peng.m...@intel.com):
Hi @Suarabh, I am profiling RF transform performance. I change transform to use 
transformImpl which uses broadcase, but find there is no performance 
improvement. 
Could you show me what is your case?  For example, the tree size, number of 
features, dataset partitions, and number of executors. Thanks. 

> RandomForest classification model not using broadcast in transform
> ------------------------------------------------------------------
>
>                 Key: SPARK-21476
>                 URL: https://issues.apache.org/jira/browse/SPARK-21476
>             Project: Spark
>          Issue Type: Bug
>          Components: ML
>    Affects Versions: 2.2.0
>            Reporter: Saurabh Agrawal
>
> I notice significant task deserialization latency while running prediction 
> with pipelines using RandomForestClassificationModel. While digging into the 
> source, found that the transform method in RandomForestClassificationModel 
> binds to its parent ProbabilisticClassificationModel and the only concrete 
> definition that RandomForestClassificationModel provides and which is 
> actually used in transform is that of predictRaw. Broadcasting is not being 
> used in predictRaw.



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

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

Reply via email to