I'll answer 1. No, we don't have any automatic monitoring of power yet. I'm currently keeping a close eye on the results on a daily basis, and I will file bugs if we get something.
- Jon On Thu, Aug 6, 2015 at 6:24 AM, Michael Henretty <[email protected]> wrote: > Excellent work Eli and John and co! A couple of questions: > > 1.) When we get a power regression, will bugs be automatically be filed in > the power component or will we have to do this manually for now? If manual, > is someone monitoring it? How do we set a baseline here for what is > acceptable power consumption? > > 2.) I'm still not seeing any visuallyLoaded data for camera. What's the > status for camera? > > 3.) I'm not seeing any red or yellow line for email. Does that mean that > email's numbers are so far below previous numbers that it is off the chart? > If so well done email! > > 4.) I'm seeing about a 5 second variance for reboot tests. Do you think > these are actual regressions, or just normal reboot variance? 5 seconds > seems like a big difference, and I wonder if we can figure out what is > going on. > > > > > On Wed, Aug 5, 2015 at 6:25 PM, Eli Perelman <[email protected]> > wrote: > >> Hello everyone, >> >> I just wanted to take a couple minutes and outline some recent changes to >> the Raptor performance dashboards available at raptor.mozilla.org. >> >> 1. As mentioned by Jon Hylands yesterday, we now have Power data for >> nightly builds against the 1GB flame-kk. >> >> 2. There is now a dedicated link for viewing only the visuallyLoaded >> regression metric for all applications. >> >> 3. App coldlaunch and reboot data is now being generated for the 1GB >> flame-kk in addition to the existing 319MB flame-kk. >> >> 4. App cold launch charts now display 2 static horizontal lines. The >> yellow line represents the 1000ms visuallyLoaded goal for applications. The >> red line represents the performance baseline for that particular app, and >> currently this is set against the 319MB flame-kk running v2.2. Example: >> >> The Clock app currently shows visuallyLoaded around 1425ms. This number >> is above the yellow line, which means the Clock isn't currently at the >> 1000ms eventual goal. This number is also above the red line, which means >> that the Clock has regressed visuallyLoaded against the 319MB flame-kk >> since v2.2. >> >> 5. Revision annotations at the bottom of each chart are now clickable. If >> you hover over the blue arrow at the bottom of the chart, you can see the >> revisions for that particular run, and clicking on the arrow will open 2 >> new windows: one for the Gaia GitHub commit, and the other for the hg Gecko >> commit. >> >> If you have questions about any of the changes or experience any >> problems, please feel free to reach out to me, or hit me up in the #raptor >> room. >> >> Thanks! >> >> Eli Perelman >> >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g >> >> >> > > > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
