New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 601652 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocked on:
issue v8:4203



Sign in to add a comment

Emscripten generated asm.js code 10x slower versus Firefox

Reported by garethmo...@gmail.com, Apr 8 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2702.2 Safari/537.36

Steps to reproduce the problem:
1. Open http://axum.graphics/EmscriptenTest/
2. Look at console output "Blobifying took.." line
3. Compare timing result of running asm.js function. On Chrome: "Blobifying took 86ms" versus Firefox Dev Edition (47.0a2 (2016-04-06)) "Blobifying took 7ms"

What is the expected behavior?
Would expect timing to be approximately similar, not order of magnitude slower.

What went wrong?
Performance of _Blobify function in http://axum.graphics/EmscriptenTest/Blob.js was 10x slower on Chrome versus Firefox, as measured with Date().getMilliseconds()

Did this work before? N/A 

Chrome version: 51.0.2702.2  Channel: canary
OS Version: 6.3
Flash Version: Shockwave Flash 21.0 r0
 
This somehow ended up in the Blink component, not sure how I managed that. Has nothing to do with Blink.

Comment 2 by jfb@chromium.org, Apr 8 2016

Cc: titzer@chromium.org bradnelson@chromium.org jfb@chromium.org
Components: -Blink Blink>JavaScript>Performance
Components: -Blink>JavaScript>Performance Blink>JavaScript>Compiler
Status: Available (was: Unconfirmed)
Labels: Performance

Comment 5 by jfb@chromium.org, Aug 3 2016

Cc: -bradnelson@chromium.org -jfb@chromium.org
Owner: bradnelson@chromium.org

Comment 6 by benhenry@google.com, Jul 14 2017

Labels: -Performance Performance-Responsiveness
Components: -Blink>JavaScript>Compiler Blink>JavaScript>WebAssembly
Labels: -OS-Windows OS-All

Comment 8 by titzer@chromium.org, Jul 17 2017

Blockedon: v8:4203

Comment 9 by titzer@chromium.org, Jul 17 2017

This will be fixed when we turn on asm.js validation.
Status: Fixed (was: Available)
Preemptively marking this as fixed, now that we have enabled asm.js validation.

Feel free to reopen if your measurements indicates that this is not fixed.

Sign in to add a comment