Closed
Bug 1726990
Opened 3 years ago
Closed 3 years ago
wasm is 4x slower after page reload
Categories
(Core :: JavaScript: WebAssembly, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1719615
People
(Reporter: jfcgauss, Unassigned)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
- serve 'web' directory with a simple web server on port 8090
- open Firefox 91.0.1
- open developer tools
- visit http://localhost:8090
- click Run button
- wait for button to enable
- click Run again (observe output in console: firefox.jpg)
- reload the page
- click Run button
- wait for button to enable
- click Run again (observe output in console: firefoxReload.jpg)
Note: my setup is Manjaro Linux, core i5 cpu. main.go compiled with Go 1.16.7
Actual results:
After reload, wasm code (a sorting test) runs 4x slower.
Expected results:
Same running time is expected after reload. See chromium.jpg and chromiumReload.jpg for the same experiment on Chromium 92.0.4515.159
Comment 2•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Javascript: WebAssembly' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Component: Untriaged → Javascript: WebAssembly
Product: Firefox → Core
with tinygo compiler v0.19.0, it is 5.5x slower after a reload.
Updated•3 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•