Storage Device Power Management via Command-Type Inactivity Timers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for setting an inactivity time period for storage devices to transition to a reduced power state fail to achieve an optimal balance between power consumption and system performance, as they do not differentiate between read and write commands, leading to either decreased performance or unnecessary power consumption.
Innovation Solution
A system and method that set distinct inactivity times based on the type of I/O commands received, with a longer inactivity time for read commands and a shorter time for write commands, allowing the storage device to transition to a reduced power state only after a predetermined idle period has passed without receiving commands, thereby optimizing power management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If a single inactivity time period is used for all I/O commands, then the power management is simple, but power consumption cannot be optimized and system performance deteriorates
Solution Approach 1:
The patent segments the single inactivity time parameter into multiple distinct inactivity time periods based on I/O command types. Specifically, it establishes a first inactivity time period for read commands and a second inactivity time period for write commands, allowing differentiated power management strategies for different operational patterns.
Solution Approach 2:
The patent implements dynamic adjustment of the inactivity time parameter based on the type of I/O command received. The system transitions from a static single inactivity time to a dynamic multi-value inactivity time that adapts to different command types (read vs. write), enabling optimal power consumption while maintaining system performance.
2Use of energy by moving object
If the inactivity time is set too short, then power consumption is reduced, but system performance decreases due to excessive recovery times
Solution Approach 1:
The patent applies different inactivity time values based on the local characteristics of I/O command types. Read commands receive a first inactivity time period while write commands receive a second inactivity time period, allowing each command type to have optimized power management tailored to its specific access patterns and performance requirements.
Solution Approach 2:
The patent changes the inactivity time parameter based on the type of I/O command received. By adjusting this critical timing parameter dynamically between a first inactivity time for reads and a second inactivity time for writes, the system optimizes both power consumption and recovery time for different operational scenarios.
3Productivity
If the inactivity time is set too long, then system performance is maintained, but power consumption increases unnecessarily
Solution Approach 1:
The patent segments the inactivity time parameter into command-type-specific values, establishing a first inactivity time for read commands and a second inactivity time for write commands. This segmentation enables the system to avoid using excessively long inactivity times that would waste power, instead applying appropriately optimized timings for each command type.
Solution Approach 2:
The patent implements dynamic selection of inactivity time based on the received I/O command type. Rather than using a uniformly long inactivity time that guarantees performance but wastes power, the system dynamically adjusts the inactivity period to match the specific characteristics of read or write commands, optimizing the power-performance balance.
Data Source
AI summary
A storage device, such as a hard disk drive or solid state drive, reduces energy consumption by entering a reduced power state after an inactivity time where the inactivity time is set based upon I/O commands received at the storage device. For example, where commands received at a storage device are characterized in a predetermined way in terms of read commands, such as a last received command as a read command or a ratio of read commands versus write commands, a first inactivity time is applied, while commands characterized in a predetermined way in terms of write commands have a second inactivity time applied. Using a greater inactivity time during read activities than during write activities provides improved performance with reduced power consumption.