[jira] [Resolved] (SPARK-17304) TaskSetManager.abortIfCompletelyBlacklisted is a perf. hotspot in scheduler benchmark

["Josh Rosen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-17304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Rosen resolved SPARK-17304.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

Issue resolved by pull request 14871
[https://github.com/apache/spark/pull/14871]

> TaskSetManager.abortIfCompletelyBlacklisted is a perf. hotspot in scheduler benchmark
> -------------------------------------------------------------------------------------
>
>                 Key: SPARK-17304
>                 URL: https://issues.apache.org/jira/browse/SPARK-17304
>             Project: Spark
>          Issue Type: Bug
>          Components: Scheduler
>    Affects Versions: 2.1.0
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> If you run
> {code}
> sc.parallelize(1 to 100000, 100000).map(identity).count()
> {code}
> then {{TaskSetManager.abortIfCompletelyBlacklisted()}} is the number-one performance hotspot in the scheduler, accounting for over half of the time. This method was introduced in SPARK-15865, so this is a performance regression in 2.1.0-SNAPSHOT.



--
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