[
https://issues.apache.org/jira/browse/SPARK-20776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-20776.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 18008
[https://github.com/apache/spark/pull/18008]
> Fix JobProgressListener perf. problems caused by empty TaskMetrics
> initialization
> ---------------------------------------------------------------------------------
>
> Key: SPARK-20776
> URL: https://issues.apache.org/jira/browse/SPARK-20776
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.2.0
> Reporter: Josh Rosen
> Assignee: Josh Rosen
> Fix For: 2.2.0
>
>
> In
> {code}
> ./bin/spark-shell --master=local[64]
> {code}
> I ran
> {code}
> sc.parallelize(1 to 100000, 100000).count()
> {code}
> and profiled the time spend in the LiveListenerBus event processing thread. I
> discovered that the majority of the time was being spent constructing empty
> TaskMetrics instances inside JobProgressListener. As I'll show in a PR, we
> can slightly simplify the code to remove the need to construct one empty
> TaskMetrics per onTaskSubmitted event.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
