Confirmed users
839
edits
Features/MobilePerformance: Difference between revisions
→Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android
No edit summary |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
== Top Goals <br> == | == Top Goals <br> == | ||
*Improve startup time | |||
*Understand memory usage <br> | *Understand memory usage <br> | ||
| Line 13: | Line 15: | ||
*Fix Panning Performance<br> | *Fix Panning Performance<br> | ||
<br> | <br> | ||
== Mobile is Everywhere<br> == | == Mobile is Everywhere<br> == | ||
| Line 33: | Line 35: | ||
*Identify what these changes are and what they cost<br> | *Identify what these changes are and what they cost<br> | ||
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn't break as Startup Shrink and | *Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn't break as Startup Shrink and MemShrink continue to make traction<br> | ||
*Non-XUL Front End Architecture? | *Non-XUL Front End Architecture? We have measurements measurements suggesting that XUL doubles are mem usage. How can we prove/disprove that? Is this fixable? <br> | ||
<br> | <br> | ||
<br> | <br> | ||
== Platform & Architecture == | == Platform & Architecture == | ||
==== Do we want to move to a single process architecture? <br> ==== | ==== Do we want to move to a single process, multithreaded architecture? <br> ==== | ||
=== P1<br> === | === P1<br> === | ||
| Line 49: | Line 51: | ||
*UI responsiveness:'''slow, no progress bar<br> ''' | *UI responsiveness:'''slow, no progress bar<br> ''' | ||
*Tap, Pan, Zoom:'''Checkerboarding<br> ''' | *Tap, Pan, Zoom:'''Checkerboarding, kinetic too jerky, poor motion profile compared to stock, font zooming delayed and ugly compared to stock<br> ''' | ||
*Memory Usage:'''We don't really know but we think it is | *Memory Usage:'''We don't really know but we think it is bad. Difficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)<br> ''' | ||
*Footprint:''' Install footprint is currently 14MB. Keep measuring this as code changes and features are added. '''<br> | *Footprint:''' Install footprint is currently 14MB. Keep measuring this as code changes and features are added. '''<br> | ||
| Line 63: | Line 65: | ||
=== P3<br> === | === P3<br> === | ||
*JavasScript:''' We are 2x faster than stock<br> ''' | * | ||
JavasScript:''' We are 2x faster than stock''' | |||
=== '''<br> '''Making Life Better for Users Today === | |||
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? <br> | *There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? <br> | ||
| Line 85: | Line 89: | ||
<br> | <br> | ||
== | == Actionable Items<br> == | ||
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&field1-0-3=rep_platform&field0-0-0=keywords&field1-0-2=op_sys&value1-0-3=ARM&type1-0-1=equals&value1-0-1=Fennec&resolution=---&type1-0-2=equals&type1-0-3=equals&value1-0-2=Android&query_format=advanced&value1-0-0=mobile&type0-0-0=substring&value0-0-0=perf&field1-0-0=keywords&field1-0-1=product&list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. <br> | *[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&field1-0-3=rep_platform&field0-0-0=keywords&field1-0-2=op_sys&value1-0-3=ARM&type1-0-1=equals&value1-0-1=Fennec&resolution=---&type1-0-2=equals&type1-0-3=equals&value1-0-2=Android&query_format=advanced&value1-0-0=mobile&type0-0-0=substring&value0-0-0=perf&field1-0-0=keywords&field1-0-1=product&list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. <br> | ||
| Line 110: | Line 114: | ||
IRC Channels?<br> | IRC Channels?<br> | ||
==== Reporting ==== | ==== Reporting ==== | ||
Where are performance metrics results reported? | |||
[http://arewefastyet.com Are We Fast Yet?]<br> | [http://arewefastyet.com Are We Fast Yet?]<br> | ||
==== Current undergoing projects happening in the interest of improving performance are:<br> ==== | ==== Current undergoing projects happening in the interest of improving performance are:<br> ==== | ||
| Line 144: | Line 150: | ||
<br> | <br> | ||
==== | ==== Domain Experts<br> ==== | ||
Mark Finkle: Mobile Front-End Lead<br> | Mark Finkle: Mobile Front-End Lead<br> | ||
Stuart | Stuart Parmenter: Pancake Lead (this is Firefox home app?)<br> | ||
Clint Talbert:& | Clint Talbert: Tools & Automation Lead | ||
Taras Gleck: Performance Manager <br> | Taras Gleck: Performance Manager <br> | ||