Storage Access Routing via Garbage Collection Awareness

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems face inefficiencies in managing access requests due to garbage collection operations, which cause latency and disrupt data access, especially when fragments in storage space are not contiguous, and existing solutions either require internal device modifications or cannot prevent small-scale garbage collection-induced latency.

Innovation Solution

A method that determines whether a garbage collection operation is being performed on a data extent within a specific address range by analyzing the association relationship between address ranges and operations, allowing access requests to be routed through storage devices not undergoing garbage collection, thereby minimizing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If garbage collection operation is performed on storage system, then free storage space is consolidated and contiguity is improved, but access request latency increases and data access speed deteriorates

Engineering Contradiction:
Improvecontiguity of free storage spaceVSAvoidaccess request latency
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The storage system is segmented into multiple storage devices, and the system identifies which specific storage devices are undergoing garbage collection operations. By segmenting the storage system at the device level rather than treating it as a monolithic unit, the system can selectively route access requests around devices performing garbage collection, thereby maintaining space consolidation benefits while minimizing access latency.

Inventive Principle:
Principle #1Segmentation

2Productivity

If access request is routed to storage device undergoing garbage collection, then load balancing is achieved, but access performance deteriorates due to garbage collection latency

Engineering Contradiction:
Improveload balancingVSAvoidaccess performance
Core Design Contradiction:
ProductivityVSSpeed

Solution Approach 1:

The system introduces an intermediary component (the identification and routing mechanism) that sits between the access request and the storage devices. This intermediary identifies which storage devices are undergoing garbage collection and redirects access requests to alternative devices, acting as a mediator that balances load across the storage system while avoiding performance degradation from garbage collection operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If existing storage system configuration is used, then system simplicity is maintained, but inability to avoid garbage collection latency persists

Engineering Contradiction:
Improvesystem configuration simplicityVSAvoidgarbage collection-induced latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The system implements a feedback mechanism where the storage management component continuously monitors the state of storage devices to identify which ones are undergoing garbage collection operations. This feedback information is then used to dynamically adjust access request routing, allowing the system to adapt to current conditions and avoid latency without requiring fundamental changes to the underlying storage configuration.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11379138B2Method, device, and computer program product for managing access request in storage system
Publication Date: 2022.07.05 EMC IP HLDG CO LLC
  • US11379138B2 patent drawing
  • US11379138B2 patent drawing
  • US11379138B2 patent drawing

AI summary

The present disclosure relates to a method, device and program product for managing an access request in a storage system. In the method, based on an access request to the storage system, an address range of a data object involved in the access request is obtained. An access type of the access request is identified in accordance with determining that a garbage collection operation is performed on a data extent within the address range. The access request is responded to based on the access type by using a data extent within an address range in the storage system on which no garbage collection operation is performed.