Storage Tier Selection for Logical Address Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data storage systems face challenges in efficiently allocating storage resources to meet performance goals for I/O operations across multiple storage tiers, particularly in selecting the appropriate RAID type and media type configuration to optimize response times and storage efficiency.

Innovation Solution

A method that involves receiving a write operation for a logical device without allocated storage, selecting a storage tier based on matching performance goals and expected performance levels, allocating physical storage, and mapping logical addresses to optimize I/O operations by determining the preferred RAID type and media type through I/O workload analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If storage is allocated from a specific RAID type and media type, then performance goals can be met, but storage flexibility and adaptability are reduced

Engineering Contradiction:
Improveperformance goal achievementVSAvoidstorage allocation flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically selects between different storage tiers (RAID 0, RAID 1, RAID 5, RAID 10, and non-RAID options) based on real-time performance goals and workload characteristics. This dynamic allocation allows the system to adapt to varying performance requirements while maintaining flexibility in storage resource utilization.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes storage allocation parameters (RAID type, media type) based on performance goals and workload analysis. By adjusting these parameters dynamically, the system can optimize for different performance scenarios without being constrained to a fixed storage configuration.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If storage is allocated without analyzing I/O workload, then allocation speed is faster, but storage efficiency and performance optimization are reduced

Engineering Contradiction:
Improveallocation speedVSAvoidstorage efficiency
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system performs preliminary analysis of I/O workload characteristics before allocating storage resources. By analyzing workload patterns in advance, the system can make informed decisions about storage tier selection, optimizing storage efficiency without significantly impacting allocation speed.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If multiple storage tiers are used to optimize performance, then response times are improved, but system complexity increases

Engineering Contradiction:
Improveresponse timeVSAvoidstorage system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system segments storage resources into multiple tiers with different performance characteristics (RAID 0 for high performance, RAID 1 for redundancy, RAID 5 for capacity, RAID 10 for balanced performance). This segmentation allows the system to optimize response times for different workload types while managing complexity through clear tier definitions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces a storage management intermediary that automatically selects appropriate storage tiers based on performance goals and workload characteristics. This intermediary layer simplifies the complexity by abstracting the decision-making process, allowing the system to leverage multiple storage tiers without requiring complex manual configuration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10095425B1Techniques for storing data
Publication Date: 2018.10.09 EMC IP HLDG CO LLC
  • US10095425B1 patent drawing
  • US10095425B1 patent drawing
  • US10095425B1 patent drawing

AI summary

Described are techniques for storing data. A write operation is received that is directed to a target logical address of a logical device where physical storage has not been allocated for the target logical address. The logical device has a service level objective denoting a performance goal to be maintained with respect to I/O operations for the logical device. A storage tier is selected from a plurality of storage tiers from which to allocate storage for storing write data of the write operation. The selecting is performed in accordance with determining a match between an expected level of performance of the storage tier and the performance goal. First physical storage is allocated from the storage tier. A logical address subrange of the logical device is mapped to the first physical storage. The write data is stored in the first physical storage at a location mapped to the target logical address.