You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Ruslan Dautkhanov (JIRA)" <ji...@apache.org> on 2017/05/18 18:01:04 UTC
[jira] [Commented] (SPARK-20776) Fix JobProgressListener perf.
problems caused by empty TaskMetrics initialization
[ https://issues.apache.org/jira/browse/SPARK-20776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016168#comment-16016168 ]
Ruslan Dautkhanov commented on SPARK-20776:
-------------------------------------------
Thank you [~joshrosen]. Would it be possible to backport this patch to Spark 2.1 as well?
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org