[SPARK-20776] Fix JobProgressListener perf. problems caused by empty TaskMetrics initialization - ASF JIRA

Rank to Top

Rank to Bottom

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 2.2.0
Fix Version/s: 2.2.0
Component/s: Spark Core
Labels:
None

Description

./bin/spark-shell --master=local[64]

I ran

  sc.parallelize(1 to 100000, 100000).count()

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.