JS demo (https://www.fxhash.xyz/generative/24521 ) is slower to load in Nightly compared to Chrome
Categories
(Core :: JavaScript Engine, task, P3)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug, )
Details
Go to https://www.fxhash.xyz/generative/24521 (Exact hash used is https://gateway.fxhash2.xyz/ipfs/QmPvPQ9mdXzdx6cSGvkqtB1ZkBqt8ajPiGWeBhQa1Jr8iz/?fxhash=oovAi2SiBCCQh5EpYX554WyVEKMkdsCNwrbYZ51vsvrxoAoZghi)
Nightly (with parallel GC marking): https://share.firefox.dev/40HYhD1
Chrome: https://share.firefox.dev/3RI8xqR
|
Reporter | |
Comment 1•2 years ago
|
||
Nightly with GC parallel marking disabled: https://share.firefox.dev/40UdvVR
|
||
Comment 2•2 years ago
|
||
The stacks in these profiles don't entirely make sense. There are instances of the GC calling back into JIT code in both of them, which never happens.
The first issue I see is that we're doing a lot of minor GCs. Maybe there's another kind of allocation we could pretenure to address this.
|
||
Updated•2 years ago
|
|
|
Reporter | |
Comment 3•1 year ago
|
||
Latest profile: https://share.firefox.dev/3JOjswf
The GC heavy part has reduced by 50% now (8.5seconds -> 4.5 seconds)
|
|
Reporter | |
Comment 4•1 year ago
|
||
All timings are for the JS heavy part of the profile:
2023-02-09 : 8.5 seconds (profile in comment #0)
Bug 1483869 part 12: 8.5seconds -> 6.5seconds
Bug 1823811: 6.5seconds - > 5.3 seconds
and if you enable parallel marking, it shaves off another 0.5 seconds
Description
•