You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/11/03 19:10:58 UTC
[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&focusedCommentId=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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org