Browse Prior Art Database

Automatic power capping

IP.com Disclosure Number: IPCOM000237671D
Publication Date: 2014-Jul-02
Document File: 2 page(s) / 89K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article introduces a mechanism of automatically setting a reasonable power capping to the server. The power capping value is based on historical server power consuming statistics which represents the actual server power usage. The mechanism eases the risk of power issues on newly shipped products and provides customer and up-level power management entities a useful reference power consumption data.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 01 of 2

Automatic power capping

The current power management mechanism includes power capping and power saving. Power savings involvesreducing the average power consumed by a component over time. The goal is to throttle the component to reduce power when performance is not needed. Peak power is typically not limited -- power is generally allowed to increase if necessary to accommodate increased workload.

Power capping involves limiting the peak power thatcan be consumed by a component. The goal is to reduce the amount of power and cooling infrastructure that must be allocated for the component. For a fixed chassis, distributing power budget to nodes by limiting nodes

'

peak

power makes more sense than power saving.

However, the current power capping from chassis to nodes is either specified by user or simply distributed by division e.g. Chassis got 2400w power and then give each 6 nodes 400w power budget. Even worse, without user

                                                                   ' s engagement, the chassis may leave with NO-POWERMANAGEMENT situation, which is a big risk that the overall power consumption may exceeds total available power.

This design describes a new mechanism that nodes can calculate its


' normal power consumption based on daily experience and automatically

cap itself to prevent peak power.

By doing that:

1. Saving power compared with the current shipped products without losing performance.

2. Prevent chassis peak power situation that may lead to psu oversubscription and node power down.

3. provides customer and up-level power management entities a usefu...