Project Candle bug triage (1st November 2015)

[Nicholas Nethercote]

Greetings,

This is Project Candle bug triage email. The process used is described at
https://wiki.mozilla.org/Performance/Project_Candle#Bug_triage_process.

At the time of writing there are 4 unprioritized Power bugs, viewable at
http://mzl.la/1KuHf1J. In this thread I am discussing all of them.


* https://bugzilla.mozilla.org/show_bug.cgi?id=885913
* We use 3x as much power as IE to scroll wikipedia

This is on Windows, and "is probably worth re-testing with APZC". I would test
but Intel Power Gadget is giving me bogus results on my Windows machine that I
haven't yet had a chance to investigate.

I suggest P2 due to the (unfortunate) lack of up-to-date data.


* https://bugzilla.mozilla.org/show_bug.cgi?id=984396
* High power consumption on Vimeo homepage (no video playing)

I suggest P2.


* https://bugzilla.mozilla.org/show_bug.cgi?id=987124
* High power consumption with WebGL

Uncompelling because the particular demo is possibly broken. I suggest P3.


* https://bugzilla.mozilla.org/show_bug.cgi?id=1219189
* Keeps radio active, battery drain

Sounds bad. P1? rnewman, mfinkle?

[Xidorn Quan]

On Mon, Nov 2, 2015 at 3:41 PM, Nicholas Nethercote
<n.neth...@gmail.com> wrote:
> * https://bugzilla.mozilla.org/show_bug.cgi?id=984396
> * High power consumption on Vimeo homepage (no video playing)
>
> I suggest P2.

You probably should mention this is only on the *old* Vimeo homepage,
because otherwise, it should be P1 since Vimeo is 180+ globally and
140+ in the U.S according to Alexa.

- Xidorn

[Richard Newman]

* https://bugzilla.mozilla.org/show_bug.cgi?id=1219189
* Keeps radio active, battery drain

Sounds bad. P1? rnewman, mfinkle?

WFM. Logs will tell the story. 

[Benjamin Smedberg]

On 11/1/2015 11:41 PM, Nicholas Nethercote wrote:
> * https://bugzilla.mozilla.org/show_bug.cgi?id=885913
> * We use 3x as much power as IE to scroll wikipedia
>
> This is on Windows, and "is probably worth re-testing with APZC". I would test
> but Intel Power Gadget is giving me bogus results on my Windows machine that I
> haven't yet had a chance to investigate.
>
> I suggest P2 due to the (unfortunate) lack of up-to-date data.

I think I disagree. This is exactly the kind of bug that matters a to
our product. If we don't have data, I'd argue that we need to make
getting the data a P1.

Admittedly, this is more important on android than on desktop, but with
evidence of a problem on a highly-visited site we should drill down and
understand what's going on.

--BDS

[Nicholas Nethercote]

Thank you to those who took part in the discussion.

On Sun, Nov 1, 2015 at 8:41 PM, Nicholas Nethercote
<n.neth...@gmail.com> wrote:
>
> * https://bugzilla.mozilla.org/show_bug.cgi?id=885913
> * We use 3x as much power as IE to scroll wikipedia
>
> This is on Windows, and "is probably worth re-testing with APZC". I would test
> but Intel Power Gadget is giving me bogus results on my Windows machine that I
> haven't yet had a chance to investigate.
>
> I suggest P2 due to the (unfortunate) lack of up-to-date data.

I gave this P1 on bsmedberg's recommendation, but up-to-date data
would help a lot.

> * https://bugzilla.mozilla.org/show_bug.cgi?id=984396
> * High power consumption on Vimeo homepage (no video playing)
>
> I suggest P2.

I did P2 and updated the title on Xidorn's suggestion.

> * https://bugzilla.mozilla.org/show_bug.cgi?id=987124
> * High power consumption with WebGL
>
> Uncompelling because the particular demo is possibly broken. I suggest P3.

I did P3.

> * https://bugzilla.mozilla.org/show_bug.cgi?id=1219189
> * Keeps radio active, battery drain
>
> Sounds bad. P1? rnewman, mfinkle?

P1 with agreement from rnewman.