Concurrent delazification cause wasteful scheduling.
Categories
(Core :: JavaScript Engine, enhancement, P1)
Tracking
()
| 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.
| Assignee | ||
Comment 1•4 years ago
|
||
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.
Comment 3•4 years ago
|
||
| bugherder | ||
Description
•