Closed Bug 947445 Opened 12 years ago Closed 10 years ago

[1.3] GuiMark3 benchmarks not at par with Android

Categories

(Firefox OS Graveyard :: Performance, defect, P4)

Product:
Firefox OS Graveyard
Component:
Performance
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(blocking-b2g:-, tracking-b2g:-)

Status:
RESOLVED WONTFIX
Project Flags:
blocking-b2g -
tracking-b2g -

People

(Reporter: mvikram, Unassigned)

Details

(Keywords: perf, Whiteboard: [c=benchmark p= s= u=])

On 1.3, on a 8610 (dual core device) the GuiMark3 benchmarks don't meet the vanilla Chrome browser numbers running on an equivalent Android build running on the same device. The URLs are: http://www.craftymind.com/factory/guimark3/bitmap/GM3_JS_Bitmap.html http://www.craftymind.com/factory/guimark3/vector/GM3_JS_Vector.html The measurements on the following build are: FFOS Android GuiMark3 Bitmap Test 36 49 GuiMark3 Vector Test 16 46 The build details are as follows: Gecko: e5147f9a670e3a315a8aedbf11c3b9672affe8a2 Gaia: e48c2025b97f26db6e23c16d72095143d731b1fa The target is to meet the Android numbers.
blocking-b2g: --- → 1.3?
Component: Gaia::Browser → General
Keywords: perf
Minusing from 1.3 as Perf goals for 1.3 don't include these Benchmarks.
blocking-b2g: 1.3? → -
Whiteboard: [c=benchmark p= s= u=]
Severity: critical → normal
Component: General → Performance
Priority: -- → P4
tracking-b2g: --- → -
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.