Closed
Bug 1769880
Opened 2 years ago
Closed 2 months ago
https://scratch.mit.edu/projects/196070469/ runs around twice as slow in Firefox vs Chrome
Categories
(Core :: JavaScript Engine: JIT, defect, P3)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jrmuizel, Unassigned)
References
(Blocks 2 open bugs)
Details
90ms vs 45ms
Most of the time is spent in Ion jitted code.
|
Reporter | |
Comment 1•2 years ago
|
||
http://llk.github.io/scratch-vm/#119615668 seems to show a similar performance difference
|
||
Comment 2•2 years ago
|
||
Profiled http://llk.github.io/scratch-vm/#196070469, producing this profile https://share.firefox.dev/3sUnPh0
Looks like a solid 30% of the execution time is spent in js::AtomizeString
Severity: -- → S3
Priority: -- → P3
|
||
Updated•2 years ago
|
Blocks: sm-defects-site, sm-runtime
|
||
Comment 3•2 years ago
•
|
||
Latest Profile: https://share.firefox.dev/3HMupxV
Visually, we are still quite slow compared to Chrome.
|
|
||
Comment 4•2 months ago
|
||
Latest profile: https://share.firefox.dev/3YNHCzt
Visually, we are similar to Chrome here.
|
||
Comment 5•2 months ago
|
||
Comparing the profiles in comment 2 and comment 4, it looks like improvements to speed up string atomization have paid off. Bug 1867359 and bug 1881995 are plausible candidates.
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•