Closed Bug 1773682 Opened 4 years ago Closed 4 years ago

Concurrent delazification cause wasteful scheduling.

Categories

(Core :: JavaScript Engine, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
103 Branch
Tracking Status
firefox103 --- fixed

People

(Reporter: nbp, Assigned: nbp)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

Concurrent delazification is currently implemented with a single DelazifyTask which is scheduled multiple times. Scheduling the task takes a lot of resources, such as clearing cached allocations, temporarily taking locks, and moving the code & data in the correct caches when the task changes thread.

Replacing this by a model where the DelazifyTask is parsing all selected functions in a single scheduled should dramatically improve latency and efficiency of DelazifyTasks.

Blocks: 1773683

Previously each function to be delazified was scheduled individually. Causing a
ton of overhead around the usage of locks and recycled memory allocations.

This change causes DelazifyTask to delazify each function within a single
schedule of the DelazifyTask, while adding the skeleton for making the
DelazifyTask interruptible in the future.

Pushed by npierron@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7799edb85c2c DelazifyTask: Aggregate all delazifications under a single task. r=arai
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: