Runfield draws slower than Chrome for Android

Nightly or Maple?

So it currently looks like runfield is hitting all of our hotpaths in canvas. Because there's no scaling happening, I expect that the canvas performance is close to being memory bandwidth bound. This means that we should be able to get performance close to what Chrome has even though it has GPU accelerated canvas. The current known problems keeping us back from full performance are: the double painting from bug 727939 and upload performance which will hopefully be improved by gralloc. The texture copy in glTexImage2d showed up very high during profiling.

In the new version of the demo, I scale the Canvas. This impacts the performance, right? I use <meta viewport="width=device-width"> and the <canvas> is scaled (width: 100%). I could also use <meta viewport="width=thesizeofthecanvas"> but I guess that would do the same thing.

Status: there is a patch in review in the related bug. P1 = needs assignee.

Jeff - I heard you had a plan for this bug. True?

(In reply to Mark Finkle (:mfinkle) from comment #5) > Jeff - I heard you had a plan for this bug. True? I assume it's bug 729266

Jeff, is this a dupe?

No, this is a tracking bug.

I made a modified Runfield demo here that makes the fox go faster: http://people.mozilla.org/~mwargers/tests/unminimized/Runfield/Runfield.htm On my Samsung Galaxy Nexus, this looks smoother to me on Fennec Nativue trunk than on Google Chrome beta.

Looks like the canavs FPS improvements have been validated