Optimization of Power and Computational Density of a Data Center
Abstract
Techniques for optimizing power and computational density of data centers are described. According to various embodiments, a benchmark test is performed by a computer data center system. Thereafter, transaction information and power consumption information associated with the performance of the benchmark test are accessed. An efficiency metric value is then generated based on the transaction information and the power consumption information. In some implementations, the efficiency metric value indicates a number of transactions executed via the computer data center system during a specific time period per unit of power consumed in executing the transactions during the specific time period. The generated efficiency metric value is then compared to a target threshold value. Thereafter, a performance summary report indicating the generated efficiency metric value, and indicating a result of the comparison of the generated efficiency metric value to the target value, is generated.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method implemented by at least one computing device, the method comprising:
determining a benchmark value of an efficiency metric for a hardware component executing as part of a computing system; generating a target value of the efficiency metric for the hardware component; determining a difference between the benchmark value of the efficiency metric and the target value of the efficiency metric; and causing output of a notification based on the difference between the benchmark value with the target value.
2 . The method of claim 1 , wherein the efficiency metric comprises power consumption data for the hardware component and the target value of the efficiency metric comprises an amount of power to be consumed by the hardware component.
3 . The method of claim 1 , wherein the efficiency metric comprises temperature data for the hardware component and the target value of the efficiency metric comprises a temperature for the hardware component.
4 . The method of claim 1 , wherein the efficiency metric comprises a cost incurred from operating the hardware component during a time period.
5 . The method of claim 1 , wherein determining the benchmark value of the efficiency metric for the hardware component is performed based on prior power consumption information for the hardware component.
6 . The method of claim 1 , wherein the hardware component comprises a computer processor.
7 . The method of claim 1 , wherein the efficiency metric comprises a number of users accessing the hardware component during a time period.
8 . A method implemented by at least one computing device, the method comprising:
determining, for each of a plurality of hardware components executing as part of a computing system, a benchmark value of an efficiency metric for the hardware component; determining, for each of the plurality of hardware components, a target value of the efficiency metric for the hardware component; computing a difference between the benchmark value of the efficiency metric and the target value of the efficiency metric for each of the plurality of hardware components; generating a report that describes the differences between the benchmark values of the efficiency metric and the target values of the efficiency metric for the plurality of hardware components; and causing output of the report at a display of a client device.
9 . The method of claim 8 , wherein the efficiency metric comprises power consumption data for the hardware component and the target value of the efficiency metric comprises an amount of power to be consumed by the hardware component.
10 . The method of claim 8 , wherein the efficiency metric comprises temperature data for the hardware component and the target value of the efficiency metric comprises a temperature for the hardware component.
11 . The method of claim 8 , wherein the efficiency metric comprises a cost incurred from operating the hardware component during a time period.
12 . The method of claim 8 , wherein determining the benchmark value of the efficiency metric for the hardware component is performed based on prior power consumption information for the hardware component.
13 . The method of claim 8 , wherein one of the plurality of hardware components comprises a computer processor.
14 . The method of claim 8 , wherein the efficiency metric comprises a number of users accessing the hardware component during a time period.
15 . A system comprising:
one or more processors; and a computer-readable storage medium storing instructions that are executed by the one or more processors to perform operations comprising:
determining a benchmark value of an efficiency metric for a hardware component executing as part of a computing system;
generating a target value of the efficiency metric for the hardware component;
determining a difference between the benchmark value of the efficiency metric and the target value of the efficiency metric; and
causing output of a notification based on the difference between the benchmark value with the target value.
16 . The system of claim 15 , wherein the efficiency metric comprises power consumption data for the hardware component and the target value of the efficiency metric comprises an amount of power to be consumed by the hardware component.
17 . The system of claim 15 , wherein the efficiency metric comprises temperature data for the hardware component and the target value of the efficiency metric comprises a temperature for the hardware component.
18 . The system of claim 15 , wherein the efficiency metric comprises a cost incurred from operating the hardware component during a time period.
19 . The system of claim 15 , wherein determining the benchmark value of the efficiency metric for the hardware component is performed based on prior power consumption information for the hardware component.
20 . The system of claim 15 , wherein the hardware component comprises a computer processor.Join the waitlist — get patent alerts
Track US2022269575A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.