Open
Bug 1847675
Opened 1 year ago
Updated 1 year ago
Codepen demo (https://codepen.io/cantelope/pen/OJaqjxd ) is visually very slow in Nightly compared to Chrome
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
Go to : https://codepen.io/cantelope/pen/OJaqjxd
Nightly: https://share.firefox.dev/3Qwjcqa
Chrome: https://share.firefox.dev/3Qwjc9E
|
Reporter | |
Comment 1•1 year ago
|
||
|
||
Updated•1 year ago
|
Severity: -- → N/A
Priority: -- → P3
|
||
Comment 2•1 year ago
|
||
Seems like a huge amount of time being spent in a self-hosted next call generated as part of array spread
sparks = [];
spawnSparks = (X, Y) => {
sparks = [...sparks, [X, Y, 1]];
};
|
||
Comment 3•1 year ago
|
||
Our current approach for optimizing this depends on inlining the next call. It looks from the profile like that didn't happen here. I think the iterator-related work we're considering might help here.
The code in question would ideally be rewritten as sparks.push([X,Y,1]), which would be easier to optimize and create less garbage.
You need to log in
before you can comment on or make changes to this bug.
Description
•