Firefox OS/Performance: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 109: Line 109:


* How to Back Out
* How to Back Out
1) update tree
** update tree
2) git revert -m1 originalCommitHash. Only need the -m1 if you the original commit was a merge.
** git revert -m1 originalCommitHash. Only need the -m1 if you the original commit was a merge.
3) git push
** git push


==Other==
==Other==

Revision as of 02:32, 12 February 2014

Firefox OS Performance

Mozilla's program for advancing Firefox OS performance.

Engineering Manager Mike Lee
Engineers Jon Hylands, Ben Kelly, Hubert Figuière, Kevin Grandon, David Huseby, Mason Chang, Geo Mealer (QA)
Product Management Ravikumar Dandu
Program Management
User Experience Gordon Brander
Location (Timezones) United States (PT & ET), Canada (ET)
Wiki https://wiki.mozilla.org/B2G/Performance
Calendar (CalDAV) https://mail.mozilla.com/dav/mozillacalendar@mozilla.com/FxOS%20Performance
Contact #fxos-perf on irc.mozilla.org, fxos-perf@mozilla.com
Stand-ups FxOS_Performance Vidyo Room: Tuesdays @ 1pm PT & Fridays @ 11am PT
Triages FxOS_Performance Vidyo Room: Wednesdays @ 11am PT
Sprint Planning FxOS_Performance Vidyo Room: 10am PT on last Friday of each sprint.

Plans

Test Coverage

Category Test area Harness Results Work
Progress First launch b2gperf, Eideticker (soon) Inari+master datazilla done
Progress Warm launch ? ? ?
Handeye FPS Eideticker underway B2G/Performance/FPS
Handeye Scrolling b2gperf Hamachi + master datazilla done
Progress Browser Page Load/Rendering ? ? ?
Effect Keyboard Key Entry Rate Eideticker (in development: bug 895952) none yet (bug 909796 underway
Power Power consumption bug 917375 none yet underway
Power Standby time bug 917375 none yet underway
? Memory use gaiatest (endurance tests) Inari+master datazilla done
? Memory use awsy bug 899194 none yet underway
? Benchmarks speedtests (octane, etc) underway underway
? Reflows ? ? ?
? Memory size of app process awsy bug 899194 none yet underway

Tools

  • How to Back Out
    • update tree
    • git revert -m1 originalCommitHash. Only need the -m1 if you the original commit was a merge.
    • git push

Other