We've published the Intel Platform Power Estimation Tool (IPPET) on the web. IPPET is a prototype power monitoring utility that uses Intel-specific energy MSRs and breaks down power consumption per process and displays them in real-time on a web browser. Another tool from Intel, the Intel Power Gadget, displays the CPU, GPU and package power over time but it doesn't spread the power used back to the processes.
The IPPET package is available at: https://software.intel.com/file/ippet-v123-setupzip
The IPPET quick start guide at https://software.intel.com/sites/default/files/managed/96/0d/ippet_quick_start_guide.docx .
- Hardware must be Sandybridge or later chip. (Tool requires energy MSRs)
- Port 8080 open for localhost connection (this should be the case by default)
- Windows 7 and 8+
- If you are using Microsoft Internet Explorer, you need version >= 9.
- IE compatibility mode doesn’t work (since it reverts IE back to ver8)
You have to use the WinRing0 driver (the WinRing0*.sys and WinRing0*.dll files) from http://www.techpowerup.com/downloads/SysInfo/Real_Temp
The source code and binary for IPPET is included in the IPPET zip.
Features of IPPET:
- Backend collects the data and optionally, using an embedded webserver, displays the data to a web browser page.
- The main IPPET GUI 'Processes' tab is a task manager like display of per process CPU, GPU, and power.
- The CPU energy MSR is used to estimate the power used over an interval and the CPU power is spread to the non-idle CPU using processes during that interval.
- The GPU energy MSR is used to estimate the power used by the GPU over the interval. IPPET calculates the %GPU_utilization for each process and spreads the GPU power according to how much each process used the GPU.
- Some pseudo processes are used to 'charge' other power. For instance, the pseudo process __pkg_overhead holds the difference between: package_overhead = package_power - cpu_power - gpu_power
- The 'Power' tab displays power usage over time. Quantities displayed:
- Package, CPU and GPU power
- GPU %utilization is charted
- Disk (SSD) power
- Battery charge/discharge rate with package power
- The 'History' tab displays power and energy usage by process over the history interval.
- you can set the interval to the last 1, 2, 5 or 15 minutes, or the entire IPPET run
- The 'Top Power' chart displays the top cumulative Power (energy actually) using processes over the history interval
- The 'Average Power' chart tells you the average power used by a process when it ran.
- The 'Battery' tab displays general battery info and estimates how much you could extend your battery life if you end a process.
- You have to be running from the battery for this tab to display info.
- The remaining battery time and %remaining is displayed.
- For each running process, we estimate how much battery life you could get back if you terminated the process.
- The GUI has lots of 'hover of a field to get explanations of how we calculate it' help.
- There are many command line options and you can change the defaults via an 'options.txt' file.
- For instance, IPPET displays the process description instead process image name. You can change the default to display the process image name if you want.
- All the data is logged and written to log files
- The logs are written when IPPET exits by default but can be written on demand.
- The 'over time' log file shows system and per process data over time. The format of this log is similar to perfmon TSV file.
- The files are given extensions .xls so I can load them into Excel easily.
- There is a 'system info' log with lots of details about the system.
The web server uses port 8080. This can be changed via options. For security, the webserver only allows localhost connections. You would have to change the source code to allow remote host connections.
- The energy MSRs are estimates of power usage.
- IPPET takes a snapshot of running processes (using EnumProcesses) every interval to see the currently running processes. If a process starts and exits between snapshots then IPPET will not see the process. This could be fixed using ETW to log process creation and destruction (with perhaps less overhead than EnumProcesses) but so far it hasn't been a problem.
- Currently runs only on Windows
- Requires a big core Sandybridge or later chip, (not Atom processor)
One of the intentions is to demonstrate how to get a 'who is burning up my battery' display like you see on smart phones. The intention is not to reinvent the task manager display... one could spend a career doing that.
Please let us know your feedback on the utility if you find it useful (or not) or if you have requests.