Estimation of power consumption of individual websites

• US 10,044,576 B2
• Filed: 11/25/2015
• Issued: 08/07/2018
• Est. Priority Date: 11/25/2015
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Arulesan, Veluppillai, Hui, Shiu Wai, Chao, Stewart
• Primary Examiner(s): HAILE, AWET A
• Application Number:
  US14/952,654
• Publication Number:
  US 20170149633A1
• Time in Patent Office: 986 Days
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3062 where the monitored property is the power consumption power management in a computing system G06F1/3203
• CPC Class Codes: G06F 11/32 with visual or acoustical indication of the functioning of the machine
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/348 Circuit details, i.e. tracer hardware
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04W 52/0254 detecting a user operation or a tactile contact or a motion of the device
• CPC Class Codes: H04W 72/0473 the resource being transmission power
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

An example method of estimating a power consumption of one or more websites includes receiving browser metrics from a browser hosted on a device. The browser metrics correspond with accessing a single website. The method also includes estimating a power consumption by the device while accessing the single website based on the browser metrics.

Claims

1. A method of estimating a power consumption of one or more websites, comprising:

receiving first browser metrics from a browser hosted on a device, the first browser metrics corresponding with accessing a first webpage of a website;

estimating a power consumption by the device while accessing the first webpage based on the first browser metrics;

receiving second browser metrics from the browser, the second browser metrics corresponding with accessing a second webpage of the website;

updating the power consumption in accordance with the second browser metrics;

adding, based on the updated power consumption, an identifier of the website to a list of websites that have been identified as power hungry websites;

detecting a request by a user of the device to access a requested webpage of the website; and

in response to detecting the request;

providing a message on a display of the device indicating that the website is a power hungry website, the message including a first user selectable option that if selected indicates that the user wishes to proceed with accessing the website and further including a second user selectable option that if selected indicates that the user does not wish to proceed with accessing the website;

in response to receiving a selection of the first user selectable option, rendering the requested webpage on a display of the device; and

in response to receiving a selection of the second user selectable option, sending an instruction to the browser to disregard the request to access the requested webpage.

2. The method of claim 1, further comprising:

receiving hardware metrics from a hardware monitor, the hardware metrics corresponding with accessing one or more of the plurality of webpages, wherein estimating the power consumption is further based on the hardware metrics.

3. The method of claim 2, wherein the hardware metrics include at least one of a process time of one or more CPUs, a CPU frequency of the one or more CPUs, GPU process time of one or more GPUs, statistics of a battery, and an amount of data downloaded to render a webpage corresponding with the accessing of the single website.

4. The method of claim 1, wherein the browser metrics include a number of client-side invocations on one or more rendered frames based on rendering one or more webpages of the plurality of webpages, the number of client-side invocations corresponding with the accessing of the one or more webpages of the plurality.

5. The method of claim 4, wherein the client-side invocations are JavaScript invocations.

6. The method of claim 1, wherein the browser metrics include an average time cost of one or more client-side invocations on one or more rendered frames based on rendering one or more webpages of the plurality of webpages, the average time cost corresponding with the accessing of the one or more webpages of the plurality.

7. The method of claim 1, wherein the browser metrics include a number of main frame commits based on rendering one or more webpages of the plurality of webpages, the number of main frame commits corresponding with the accessing of the one or more webpages of the plurality.

8. The method of claim 1, wherein the browser metrics include a number of compositing cycles triggered based on rendering one or more webpages of the plurality of webpages, the number of compositing cycles corresponding with the accessing of the one or more webpages of the plurality.

9. The method of claim 1, wherein the browser metrics include an average time cost of compositing cycles based on rendering one or more webpages of the plurality of webpages, the average time cost of compositing cycles corresponding with the accessing of the one or more webpages of the plurality.

10. The method of claim 1, wherein the browser metrics include a number of rendered request animation frame (rAF) elements based on rendering one or more webpages of the plurality of webpages, the number of rAF elements corresponding with the accessing of the one or more webpages of the plurality.

11. The method of claim 1, wherein the browser metrics include a number of texture uploads generated based on rendering one or more webpages of the plurality of webpages, the number of texture uploads corresponding with the accessing of the one or more webpages of the plurality.

12. The method of claim 1, wherein the browser metrics include at least one of an average time cost of main frame commits based on rendering one or more webpages of the plurality of webpages, an average time cost of client-side invocations on one or more Web-worker threads based on rendering one or more webpages of the plurality, network bandwidth required based on rendering one or more webpages of the plurality, a number of image bytes to be decoded based on rendering one or more webpages of the plurality, a number of rendered video elements based on rendering one or more webpages of the plurality, a number of graphic layers created based on rendering one or more webpages of the plurality, an average time cost of rasterization based on rendering one or more webpages of the plurality, and a number of rendered animating elements based on rendering one or more webpages of the plurality.

13. The system of claim 1, wherein the operations further comprise:

maintaining the list of websites that have been identified as power hungry websites, wherein the estimated power consumption is less than a threshold and the updated power consumption is not less than the threshold.

14. The method of claim 13, further comprising:

removing the identifier of the website from the list of websites if a second updated power consumption associated with the website is less than the threshold.

15. A system for estimating a power consumption of one or more websites, comprising:

a non-transitory memory; and

one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising;

receiving first browser metrics from a browser hosted on a device, wherein the first browser metrics correspond with accessing a first webpage of a website;

estimating a power consumption by the device while accessing the first webpage based on the first browser metrics;

receiving second browser metrics from the browser, wherein the second browser metrics correspond with accessing a second webpage of the website;

updating the power consumption in accordance with the second browser metrics;

adding, based on the updated power consumption, an identifier of the website to a list of websites that have been identified as power hungry websites;

detecting a request by a user of the device to access a requested webpage of the website; and

in response to detecting the request;

providing a message on a display of the device indicating that the website is a power hungry website, the message including a first user selectable option that if selected indicates that the user wishes to proceed with accessing the website and further including a second user selectable option that if selected indicates that the user does not wish to proceed with accessing the website;

in response to receiving a selection of the first user selectable option, rendering the requested webpage on a display of the device; and

in response to receiving a selection of the second user selectable option, sending an instruction to the browser to disregard the request to access the requested webpage.

16. The system of claim 15, wherein the operations further comprise:

monitoring a hardware monitor that monitors hardware metrics of hardware coupled to the device, wherein the hardware metrics correspond with the accessing one or more of the plurality of webpages of the single web site, and wherein the estimating includes estimating the power consumption based on the hardware metrics.

17. The system of claim 15, wherein the device is a mobile device.

18. The system of claim 15, wherein the browser metrics include a number of client-side invocations on one or more rendered frames based on rendering one or more webpages of the plurality of webpages, the number of client-side invocations corresponding with the accessing of the one or more webpages of the plurality.

19. The system of claim 15, wherein the browser metrics include a number of main frame commits based on rendering one or more webpages of the plurality of webpages, the number of main frame commits corresponding with the accessing of the one or more webpages of the plurality.

20. The system of claim 15, wherein the browser metrics include a number of compositing cycles triggered based on rendering one or more webpages of the plurality, the number of compositing cycles corresponding with the accessing of the one or more webpages of the plurality.