JS demo (https://www.fxhash.xyz/generative/19596 ) takes half the time to load in Chrome compared to Nightly
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/19596 (The exact hash is profiled is https://gateway.fxhash2.xyz/ipfs/QmaYyWpvzuLn8aPB7V4bX4GxyUKmKeoz1nDmSfZmTytZHE/?fxhash=ooaotgDQD5C11PgwDs7386ydt2J7RJAEYndfTnW9vYsLSSYSWwh)
Click on "Open"
Nightly: https://share.firefox.dev/3RgRv2J (67 seconds to load)
Chrome (Partial profile of first 10 seconds) : https://share.firefox.dev/3Y5R7GK ( Took 29 seconds wall clock time)
Updated•2 years ago
|
Reporter | ||
Comment 2•2 years ago
|
||
Profile with the latest Nightly: https://share.firefox.dev/3SypGUa
Comment 3•2 years ago
|
||
What times are you seeing now, compared to the 67 seconds in comment 0? I don't see anything related to bound function calls in your latest profile, so that suggests the JIT optimization for it works.
Comment 4•2 years ago
|
||
There are other things too, for example some very slow Math.hypot
calls because the JIT isn't optimizing them for some reason.
Reporter | ||
Comment 5•2 years ago
•
|
||
(In reply to Jan de Mooij [:jandem] from comment #3)
What times are you seeing now, compared to the 67 seconds in comment 0? I don't see anything related to bound function calls in your latest profile, so that suggests the JIT optimization for it works.
It is now ~55 seconds (what the profiler shows) and ~44 second wall-clock time
Chrome is 23-30 second (wall-clock time)
Updated•2 years ago
|
Reporter | ||
Comment 6•4 months ago
•
|
||
Nightly: https://share.firefox.dev/3W5FaS5 (36s with profiler, 26s wall clock)
Chrome: https://share.firefox.dev/4f4jdeu (20s with profiler 16s wall clock)
Description
•