Open
Bug 806576
Opened 12 years ago
Updated 2 years ago
IonMonkey: Investigate x86 and ARM disparity on benchmarks
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: dvander, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ion:p1])
On x86, IonMonkey and v8 are roughly the same speed (give or take a few milliseconds). On ARM, IonMonkey is roughly 25-30% slower. We need to find out why. There are a few test cases where it's particularly noticeable:
kraken-gaussian-blur
x86: 190ms for Ion, 193ms for v8
ARM: 6812ms for Ion, 1427ms for v8
kraken-beat-detection
x86: 228ms for Ion, 193ms for v8
ARM: 2194ms for Ion, 1538ms for v8
kraken-desaturate
x86: 110ms for Ion, 110ms for v8
ARM: 5592ms for Ion, 4260ms for v8
kraken-gaussian-blur looks like it has the largest disparity.
Comment 1•12 years ago
|
||
Is this still valid?
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•