Re: power use on Yosemite
On Nov 3, 2014, at 1:44 PM, rviti...@mozilla.com wrote: In particular Facebook, which practically appears in any top 10 list, had (has?) a serious power bug that caused FF to render a hidden spinning wheel. Because of this single bug any power benchmark performed by the press, which was likely going to be based on the top N most visited sites on the web, was likely going to be skewed significantly to our loss. This is bug 962594; I pushed in a fix last week. Debugging the problem revealed that some simple architectural changes could let us solve not only this bug but the entire category of related bugs (there are more; see for example bug 987212) in a very clean way. It will take some time to get the pieces into place, but we should be much more efficient in our handling of non-visible animated images soon. Thanks for identifying these problems and pushing to get them fixed, Roberto! - Seth ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: power use on Yosemite
On 02/11/14 18:13, Mike Hoye wrote: We found that blocking on a slow connection used consistently more power than idle. This could be solely due to network traffic, but network traffic was very periodic (1 packet in and 1 packet out per second), thus much of the work could likely be attributed to the animated spinner. The difference was not very large, but it was statistically significant. That suggests that it could be a result of us not having QUIC and Google Sheets not being friendly to TCP-based usages. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: power use on Yosemite
On 2014-11-03 12:32 PM, Martin Thomson wrote: On 02/11/14 18:13, Mike Hoye wrote: We found that blocking on a slow connection used consistently more power than idle. This could be solely due to network traffic, but network traffic was very periodic (1 packet in and 1 packet out per second), thus much of the work could likely be attributed to the animated spinner. The difference was not very large, but it was statistically significant. That suggests that it could be a result of us not having QUIC and Google Sheets not being friendly to TCP-based usages. These results come from a Fennec profiling exercise run against a generic but tightly throttled web server, not desktop/gdocs. - mhoye ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: power use on Yosemite
On Saturday, November 1, 2014 7:48:11 PM UTC, Andreas Gal wrote: I am using Nightly on Yosemite and power use is pretty atrocious. The battery menu tags Firefox Nightly as a significant battery hog, and I can confirm this from the user experience perspective as well. My battery time is a fraction of using Chrome for the same tasks. Not every kind of content seems to trigger this behavior, but Google Sheets in Firefox seems to be a pretty reliable way to drain my battery quickly. Andreas, I used energia (https://github.com/mozilla/energia) to quickly compare the power usage of Nightly vs Chrome on Google Sheets (https://docs.google.com/spreadsheet/ccc?key=0ArS97F99-BEZdF81LXlRNnRJTWphQ3pZcTYxT3NSRXc#gid=0 and other similar sheets) and even though the usage of FF is greater than Chrome, it's not dramatically so, i.e.: Chrome: 2.8W +- 0.03 (confidence interval of the mean) Nightly: 3.1 +- 0.22 The numbers comprehend CPU and GPU usage. Do you have by chance a particular sheet that triggers the issue which you could share? I am going to dig deeper first thing in the morning; there is some suspicious high variance in the measurements for FF. On Monday, November 3, 2014 5:33:11 PM UTC, Martin Thomson wrote: On 02/11/14 18:13, Mike Hoye wrote: We found that blocking on a slow connection used consistently more power than idle. This could be solely due to network traffic, but network traffic was very periodic (1 packet in and 1 packet out per second), thus much of the work could likely be attributed to the animated spinner. The difference was not very large, but it was statistically significant. That suggests that it could be a result of us not having QUIC and Google Sheets not being friendly to TCP-based usages. We tracked down many power bugs on Desktop earlier this year using our power profiler, see Bug 948528, Bug 962573, http://robertovitillo.com/2014/01/21/a-matter-of-energy/ and https://github.com/mozilla/energia. Many of those bugs are intimately related to the layout stack and still need to be addressed. David, do you have an ETA for some of them, e.g. Bug 962594? In particular Facebook, which practically appears in any top 10 list, had (has?) a serious power bug that caused FF to render a hidden spinning wheel. Because of this single bug any power benchmark performed by the press, which was likely going to be based on the top N most visited sites on the web, was likely going to be skewed significantly to our loss. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: power use on Yosemite
On 2014-11-01 3:47 PM, Andreas Gal wrote: Ideas welcome. Before he left, Taras was discussing power consumption analysis with Abram Hindle, a researcher at the university of Alberta. Some of Hindle's work is here: http://softwareprocess.es/static/GreenMining.html Specifically this paper: Green Mining: A Methodology of Relating Software Change to Power Consumption http://softwareprocess.es/a/green-change-web.pdf He's written a comparable paper targeting Fennec, and has interesting preliminary findings. From his email to me: We found that blocking on a slow connection used consistently more power than idle. This could be solely due to network traffic, but network traffic was very periodic (1 packet in and 1 packet out per second), thus much of the work could likely be attributed to the animated spinner. The difference was not very large, but it was statistically significant. I spoke to him today at CSER, and despite Taras' departure he'd like to continue this work that would give us a very fine-grained understanding of where your battery's going, and which we could integrate into our build infra. So that's interesting. I'll forward his papers to you directly. - mhoye ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
power use on Yosemite
I am using Nightly on Yosemite and power use is pretty atrocious. The battery menu tags Firefox Nightly as a significant battery hog, and I can confirm this from the user experience perspective as well. My battery time is a fraction of using Chrome for the same tasks. Not every kind of content seems to trigger this behavior, but Google Sheets in Firefox seems to be a pretty reliable way to drain my battery quickly. I checked with Instruments and I don’t think CPU utilization per se is the problem. We use less CPU than Chrome, especially if you add up all the many Chrome processes. Our CPU utilization is better than Chrome’s but our battery behavior is much worse. That’s really odd. Ideas welcome. Thanks, Andreas ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: power use on Yosemite
On Sat, Nov 1, 2014 at 12:47 PM, Andreas Gal andreas@gmail.com wrote: I am using Nightly on Yosemite and power use is pretty atrocious. The battery menu tags Firefox Nightly as a significant battery hog, and I can confirm this from the user experience perspective as well. My battery time is a fraction of using Chrome for the same tasks. Not every kind of content seems to trigger this behavior, but Google Sheets in Firefox seems to be a pretty reliable way to drain my battery quickly. I checked with Instruments and I don’t think CPU utilization per se is the problem. We use less CPU than Chrome, especially if you add up all the many Chrome processes. Our CPU utilization is better than Chrome’s but our battery behavior is much worse. That’s really odd. Ideas welcome. Thanks, Andreas ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform Are we using the discrete GPU when Chrome is not? - Kyle ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: power use on Yosemite
Are we using the discrete GPU when Chrome is not? That was my first guess as well. As far as I can tell we fall back to integrated GPU just fine, according to the Activity Monitor. Even App Nap seems to work when FF is occluded. Yet, our avg energy impact is 5x of Chrome. Andreas - Kyle ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
