System and method for energy usage accounting in software applications

• US 10,013,511 B2
• Filed: 04/09/2013
• Issued: 07/03/2018
• Est. Priority Date: 04/09/2012
• Status: Active Grant

• Current Assignee: Purdue Research Foundation (The Trustees of Purdue University (d/b/a Purdue University))
• Original Assignee: Purdue Research Foundation (The Trustees of Purdue University (d/b/a Purdue University))
• Inventors: Hu, Yu Charlie, Pathak, Abhinav
• Primary Examiner(s): Kim, Eunhee
• Application Number:
  US13/859,690
• Publication Number:
  US 20130268257A1
• Time in Patent Office: 1,911 Days
• Field of Search: 703 22, 702 61
• 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/3409 for performance assessment
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 30/20 Design optimisation, verification or simulation optimisation, verification or simulation of circuit designs G06F30/30
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A method for generating an energy usage profile for a software program executed in a computing device includes generating a call trace of an executed system call, identifying a first power consumption and duration of a first power state due to the first system call using a model, identifying a second power consumption and duration of a second power state based on the model, and generating an energy usage profile for the software program. The energy usage profile includes energy consumption of the computing device for the system call based on the first power consumption level multiplied by the first duration and the second power consumption level multiplied by the second duration associated an identifier for the call trace.

Claims

1. A method for generating an energy usage profile comprising:

executing program instructions corresponding to a first system call in a software program with a processor in a computing device, the processor operating a component that consumes power in the computing device in response to execution of the first system call;

generating a first call trace of the execution of the first system call with the processor, the generation of the first call trace further comprising;

generating a first timestamp corresponding to a first time at which the first system call is executed; and

generating a first identifier comprising at least one of the group consisting of a calling routine identifier, a thread identifier, and a process identifier for the software program that executes the first system call;

executing program instructions corresponding to a second system call in the software program with the processor in the computing device, the processor operating the component that consumes power in the computing device in response to execution of the second system call;

generating a second call trace of the execution of the second system call with the processor, the generation of the second call trace further comprising;

generating a second timestamp corresponding to a second time at which the second system call is executed; and

generating a second identifier comprising at least one of the group consisting of a calling routine identifier, a thread identifier, and a process identifier for the software program that executes the second system call;

identifying a first power consumption level of the component and a first duration of the first power consumption level during the first system call based on the first call trace and a first power state in a model stored in a first memory;

identifying a second power consumption level of the component and a second duration of the second power consumption level that occurs after completion of the first system call and prior to executing the program instructions corresponding to the second system call based on a second power state in the model, the first time stamp, the first duration, and the second timestamp;

identifying a third power consumption level of the component and a third duration of the third power consumption level during the second system call based on the second call trace and the first power state in the model;

identifying a fourth power consumption level of the component and a fourth duration of the fourth power consumption level that occurs after completion of the second system call based on the second power state in the model;

generating an energy usage profile for the software program associating the first identifier with an estimate of energy consumption of the component in response to the execution of the first system call based on the first power consumption level and the first duration and the second power consumption level and the second duration;

generating the energy usage profile for the software program associating the second identifier with another estimate of energy consumption of the component in response to the execution of the second system call based on the on the third power consumption level and the third duration and the fourth power consumption level and the fourth duration; and

storing the energy usage profile in a second memory.

2. The method of claim 1 wherein the first memory is the second memory.

3. A method for generating an energy usage profile in a computing device comprising:

executing program instructions corresponding to a wake lock acquire system call in the software program with a processor in the computing device, a component that consumes power in response to the wake lock acquire system call in the computing device transitioning from a first power consumption level corresponding to a first power state in a model stored in a memory of the computing device to a second power consumption level corresponding to a second power state in the model stored in the memory of the computing device in response to the execution of the wake lock acquire system call, the second power consumption level being higher than the first power consumption level;

generating a first call trace of the execution of the wake lock acquire system call with the processor, the generation of the first call trace further comprising;

generating a first timestamp corresponding to a first time at which the wake lock acquire system call is executed; and

generating a first identifier comprising at least one of the group consisting of a calling routine identifier, a thread identifier, and a process identifier for the software program that executes the wake lock acquire system call;

executing program instructions corresponding to a wake lock release system call in the software program with the processor in the computing device, the component in the computing device transitioning from the second power state to the first power state in response to the execution of the wake lock release system call;

generating a second call trace of the execution of the wake lock release system call with the processor, the generation of the second call trace further comprising;

generating a second timestamp corresponding to a second time at which the wake lock release system call is executed; and

generating a second identifier comprising at least one of the group consisting of a calling routine identifier, a thread identifier, and a process identifier for the software program that executes the wake lock release system call;

generating an energy usage profile for the software program associating the first identifier and an estimate of energy consumption of the component in the computing device in response to the execution of the wake lock acquire system call based at least in part on the power consumption level of the second power state and an elapsed time from the first timestamp to the second timestamp; and

storing the energy usage profile in a memory.

4. The method of claim 3, the generation of the energy usage profile for the software program further comprising:

generating a notification that the processor did not execute the wake lock release system call within a predetermined time in association with the first identifier in response to the elapsed time between the wake lock acquire system call and the wake lock release system call exceeding a predetermined threshold.

5. The method of claim 3, the generation of the energy usage profile for the software program further comprising:

generating a notification in association with the calling routine identifier from the first call trace indicating that the processor did not execute the wake lock acquire system call and the wake lock release system call using a single calling routine in response to identifying that the calling routine identifier in the first call trace does not correspond to the calling routine identifier in the second call trace.

6. The method of claim 3, the generation of the energy usage profile for the software program further comprising:

generating a notification in association with the thread identifier from the first call trace indicating that the processor did not execute the wake lock acquire system call and the wake lock release system call using a single thread in response to identifying that the thread identifier in the first call trace does not correspond to the thread identifier in the second call trace.

7. The method of claim 3, the generation of the energy usage profile for the software program further comprising:

generating a notification in association with the process identifier from the first call trace indicating that the processor did not execute the wake lock acquire system call and the wake lock release system call using a single process in response to identifying that the process identifier in the first call trace does not correspond to the process identifier in the second call trace.

8. The method of claim 3, the generation of the energy usage profile for the software program further comprising:

generating a notification in association with the first identifier from the first call trace indicating that the processor did not execute the wake lock release system call in response to identifying that the software program exits without execution of the wake lock release system call.

9. A system for generation of an energy usage profile in a computing device comprising:

a memory configured to store;

programmed instructions corresponding to an operating system;

programmed instructions corresponding to a user program; and

data corresponding to a model of power states corresponding to a component in the computing device;

a processor operatively connected to the memory;

a component connected to the processor to enable the processor to communicate with the component; and

the processor being configured to;

execute the programmed instructions corresponding to a first system call in the user program, the processor operating the component that consumes power in the computing device in response to execution of the first system call;

generate a first call trace of the execution of the first system call with the operating system, the processor being further configured to;

generate a first timestamp corresponding to a first time at which the first system call is executed; and

generate a first identifier comprising at least one of the group consisting of a calling routine identifier, a thread identifier, and a process identifier for the software program that executes the first system call;

identify a first power consumption level of the component and a first duration of the first power consumption level in response to execution of the first system call based on a first power state in the model;

identify a second power consumption level of the component and a second duration of the second power consumption level in response to execution of the first system call based on a second power state in the model, the component entering the second power state after the first power state;

execute programmed instructions corresponding to a second system call in the user program, the processor operating the component that consumes power in the computing device in response to execution of the second system call;

generate a second call trace of the execution of the second system call with the operating system, the processor being further configured to;

generate a second timestamp corresponding to a second time at which the second system call is executed; and

generate a second identifier comprising at least one of the group consisting of a calling routine identifier, a thread identifier, and a process identifier for the software program that executes the second system call;

identify the first power consumption level of the component and a third duration of the first power consumption level in the first power state in response to execution of the second system call based on the model stored in the memory;

identify that the second system call enters the first power state during the first duration of the first system call in response to the second timestamp occurring after the first timestamp during the first duration;

identify a first extended duration for the first power consumption level of the component corresponding to the first power state based on a portion of the first duration of the first power state for the first system call that overlaps with the second duration of the first power state for the second system call;

identify a second extended duration for the first power consumption level of the component for the second system call based on a portion of the second duration for the second system call that overlaps with the first duration for the first system call;

generate an energy usage profile for the software program associating the first identifier with an estimate of energy consumption of the component in the computing device in response to the execution of the first system call based at least in part on the first power consumption level, the first duration, the second power consumption level, and the second duration in response to a time corresponding to the first extended duration after the first timestamp being later than another time corresponding to the second extended duration after the second timestamp;

generate the energy usage profile for the software program associating the second identifier with another estimate of energy consumption of the component in the computing device in response to the execution of the second system call based on only the first power consumption level and the third duration in response to the time corresponding to the first extended duration after the first timestamp being later than another time corresponding to the second extended duration after the second timestamp; and

store the energy usage profile in the memory.

10. The system of claim 9, the processor being further configured to:

generate the energy usage profile for the software program associating the first identifier with the estimate of energy consumption of the component in response to the execution of the first system call based on only the first power consumption level and the first duration in response to the time corresponding to the first extended duration added to the first timestamp being earlier than the other time corresponding to the third duration added to the second timestamp; and

generate the energy usage profile for the software program associating the second identifier with the estimate of the energy consumption of the component in response to the execution of the second system call based at least in part on the first power consumption level, the third duration, the second power consumption level, and the second duration in response to the time corresponding to the first extended duration after the first timestamp being earlier than the other time corresponding to the third duration after the second timestamp.

11. The system of claim 9 the processor being further configured to:

double a portion of the first duration that corresponds to an overlapping time span beginning at the second time of execution for the second system call to identify the extended first duration.