Closed
Bug 1830387
Opened 2 years ago
Closed 2 years ago
Consider expanding IIFE heuristic for eager-parse.
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mgaudet, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sp3])
Attachments
(5 files)
V8 has a slightly different eager parse heuristic than us. We should investigate if matching their heuristic works to our advantage.
|
Reporter | |
Comment 1•2 years ago
|
||
|
|
Reporter | |
Comment 2•2 years ago
|
||
Depends on D176701
|
|
Reporter | |
Comment 3•2 years ago
|
||
Depends on D176702
|
|
Reporter | |
Comment 4•2 years ago
|
||
Depends on D176703
|
|
Reporter | |
Comment 5•2 years ago
|
||
Depends on D176704
|
|
Reporter | |
Comment 6•2 years ago
|
||
On Speedometer locally I measure an increase of 1100 functions over speedometer getting the IIFE heuristic eager parse with the IIFE modifications vs. without, starting from a baseline of 11210 getting the IIFE eager parse.
So the heuristic increases the number of eagerly parsed functions by 10%, which seems to not move the needle on our benchmarks.
I think we'll resolve this as WONTFIX for now.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
|
||
Updated•2 years ago
|
Whiteboard: [sp3]
You need to log in
before you can comment on or make changes to this bug.
Description
•