GPU Power Reporting API for Priority Workload Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data centers face inefficiencies in allocating power to processors due to variations in power consumption among GPUs, leading to either overallocation or underallocation of power for high-priority workloads, which is not accurately determined by current scheduling systems.

Innovation Solution

Implementing an application programming interface (API) that allows GPUs to report their power consumption at specific frequencies, enabling the scheduler to accurately determine the total power needed for high-priority workloads and allocate resources efficiently among GPUs with different power consumption profiles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If power is allocated evenly amongst processors, then allocation simplicity is maintained, but power efficiency deteriorates due to variations in actual power consumption among GPUs

Engineering Contradiction:
Improveallocation simplicityVSAvoidpower efficiency
Core Design Contradiction:
Ease of manufactureVSUse of energy by moving object

Solution Approach 1:

The system implements feedback by having GPUs report their actual power consumption through an API call. The scheduler receives this power consumption information and uses it to adjust power allocation dynamically, transforming the static even-distribution approach into a dynamic feedback-driven allocation system that adapts to actual GPU power needs.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The invention changes the allocation parameter from a uniform power distribution to a differentiated power allocation based on actual power consumption characteristics. By introducing power consumption reports from individual GPUs, the system transitions from allocating equal power to all processors to allocating power proportional to each GPU's actual consumption profile and workload requirements.

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If power allocation is based on uniform distribution, then implementation complexity is reduced, but workload performance deteriorates due to inaccurate power determination for high-priority tasks

Engineering Contradiction:
Improveimplementation complexityVSAvoidworkload performance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The scheduler implements feedback by receiving power consumption reports from GPUs through API calls. This feedback mechanism provides accurate information about actual power usage, enabling the scheduler to make informed decisions about power allocation for high-priority workloads without requiring complex predictive models or assumptions about GPU power characteristics.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary action by obtaining power consumption information from GPUs before making allocation decisions. The API call to retrieve power consumption data happens in advance, allowing the scheduler to prepare accurate power allocation plans for high-priority workloads before they are executed, rather than reacting to power issues after they occur.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If detailed power consumption tracking is implemented, then power allocation accuracy is improved, but system complexity increases due to additional API calls and data collection

Engineering Contradiction:
Improvepower allocation accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The GPU serves itself by automatically reporting its power consumption through the API call. This self-service approach eliminates the need for external monitoring hardware or complex measurement systems, as each GPU provides its own power consumption data directly to the scheduler, simplifying the overall system architecture while maintaining high measurement precision.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The API mechanism serves multiple functions: it retrieves power consumption data, provides information for scheduling decisions, and enables dynamic power allocation. This multi-functional approach consolidates what could be multiple separate systems into a single unified interface, reducing system complexity while achieving accurate power measurement and allocation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250298449A1Application programming interface to indicate power
Publication Date: 2025.09.25 NVIDIA CORP
  • US20250298449A1 patent drawing
  • US20250298449A1 patent drawing
  • US20250298449A1 patent drawing

AI summary

Apparatuses, systems, and techniques to perform an application programming interface (API) to indicate an amount of power to be consumed by one or more processors. As an example, one or more processors comprising one or more circuits to perform an API to indicate an amount of power to be consumed by one or more processors as a result of operating said one or more processors at a first clock frequency.