[jira] [Commented] (SPARK-18256) Improve performance of event log replay in HistoryServer based on profiler results
[ https://issues.apache.org/jira/browse/SPARK-18256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653501#comment-15653501 ] Vinayak Joshi commented on SPARK-18256: --- Hi - this kind of compliments the log replay improvement in https://issues.apache.org/jira/browse/SPARK-18256. SPARK-18256 got marked as Fix Version 2.1. Curious, if there's a reason that this instead has been marked as Fix Version: 2.2 and can not be 2.1 as well? > Improve performance of event log replay in HistoryServer based on profiler > results > -- > > Key: SPARK-18256 > URL: https://issues.apache.org/jira/browse/SPARK-18256 > Project: Spark > Issue Type: Improvement >Reporter: Josh Rosen >Assignee: Josh Rosen > Fix For: 2.2.0 > > > Profiling event log replay in the HistoryServer reveals Json4S control flow > exceptions and `Utils.getFormattedClassName` calls as significant > bottlenecks. Eliminating these halves the time to replay long event logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-18256) Improve performance of event log replay in HistoryServer based on profiler results
[ https://issues.apache.org/jira/browse/SPARK-18256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15633888#comment-15633888 ] Apache Spark commented on SPARK-18256: -- User 'JoshRosen' has created a pull request for this issue: https://github.com/apache/spark/pull/15756 > Improve performance of event log replay in HistoryServer based on profiler > results > -- > > Key: SPARK-18256 > URL: https://issues.apache.org/jira/browse/SPARK-18256 > Project: Spark > Issue Type: Improvement >Reporter: Josh Rosen >Assignee: Josh Rosen > > Profiling event log replay in the HistoryServer reveals Json4S control flow > exceptions and `Utils.getFormattedClassName` calls as significant > bottlenecks. Eliminating these halves the time to replay long event logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
