Open
Bug 1870486
Opened 1 year ago
Updated 3 months ago
WASM demo (https://www.fxhash.xyz/generative/28947 ) is slower in Nightly compared to Chrome
Categories
(Core :: JavaScript: WebAssembly, task, P3)
Core
JavaScript: WebAssembly
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
43.92 KB,
text/plain
|
Details |
Go to https://www.fxhash.xyz/generative/28947
Click on run
Nightly: https://share.firefox.dev/3NSNbqf (4.5s)
Chrome: https://share.firefox.dev/3TuZHji (3s)
Reporter | ||
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
Two things here:
- The profiler shows that entire thing is run in one function
$main::art::h55a937f259a0de0d
, so tiering is not working here and it never reaches the Ion - The HTTP caching is not working since the code is loaded via
data:application/wasm;charset=utf-8;base64,AGFzb...
URL
The calculation kicks in immediately and not giving a change for Ion to execute and there is no caching ability. The size of the Wasm is 1.5MB. It works fast when run with baseline disabled.
It is easy to address the issue for the application by loading Wasm via instantiateStream from HTTP resource and/or load it before the "run" button is clicked.
Updated•1 year ago
|
Severity: -- → S3
Priority: -- → P3
Updated•1 year ago
|
Blocks: wasm-perf-gap
Reporter | ||
Comment 3•1 year ago
|
||
Profile with latest Nightly: https://share.firefox.dev/3wYDKjn
Reporter | ||
Updated•3 months ago
|
Type: enhancement → task
You need to log in
before you can comment on or make changes to this bug.
Description
•