Front-End Cache Preloading for Cold Storage Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Multitier storage systems face performance degradation during cold cache events, such as power failures or data corruption, leading to prolonged recovery times due to inefficient data tier access and retrieval processes.

Innovation Solution

A computer-implemented method and system that identifies hot data within a multi-tiered data array, comprising a faster data tier with flash storage, a medium tier with fiber channel storage, and a slower tier with SATA storage, and uses a front-end cache system to populate data from the faster tier, reducing access times and enhancing overall system performance by preloading frequently accessed data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is stored in slower tiers (SATA storage) to reduce cost, then storage capacity is improved, but data access speed deteriorates during cold cache events

Engineering Contradiction:
Improvestorage capacityVSAvoiddata access speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The system proactively identifies hot data from slower tiers and pre-loads it into faster cache tiers before actual access is needed. This preliminary action ensures that when cold cache events occur, the data is already positioned in high-speed storage, eliminating the speed penalty that would normally accompany accessing data from slower storage tiers.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediate cache tier (flash storage) between the slower SATA storage and the front-end cache. This intermediary layer acts as a buffer that can rapidly serve frequently accessed data, reducing the need to access the slower SATA tier and thereby improving overall data access speed while maintaining storage capacity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If data is kept in faster tiers (flash storage) to improve access speed, then data retrieval time is reduced, but storage capacity is reduced

Engineering Contradiction:
Improvedata retrieval timeVSAvoidstorage capacity
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system applies local quality by placing only the most frequently accessed data (hot data) in the faster flash storage tiers, while less frequently accessed data remains in the slower SATA storage. This selective placement optimizes the use of expensive high-speed storage by dedicating it specifically to data that benefits most from fast access, thereby achieving improved retrieval times for critical data without unnecessarily reducing overall storage capacity.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system proactively identifies and pre-loads hot data from slower tiers into faster tiers before access is needed. This preliminary action ensures that when data is accessed, it is already positioned in high-speed storage, effectively reducing retrieval time for frequently accessed data without requiring all data to be stored in fast storage simultaneously.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If all data is loaded into front-end cache to eliminate cold cache events, then access time is improved, but system complexity and resource consumption increase

Engineering Contradiction:
Improveaccess timeVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system applies local quality by differentiating between hot and cold data, and applying different storage strategies to each. Hot data is proactively pre-loaded into the front-end cache, while cold data remains in the multi-tiered storage system. This selective approach improves access time for frequently accessed data without requiring all data to be loaded into the cache, thereby avoiding the excessive resource consumption and system complexity that would result from loading all data.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system applies partial action by loading only a subset of data (hot data) into the front-end cache rather than all data. This partial loading strategy is sufficient to eliminate cold cache events for the most critical data while avoiding the excessive resource consumption and system complexity that would result from loading all data into the cache.

Inventive Principle:
Principle #16Partial or excessive action

4Productivity

If multi-tiered storage architecture is implemented to balance performance and capacity, then storage efficiency is improved, but data tier access complexity increases

Engineering Contradiction:
Improvestorage efficiencyVSAvoiddata tier access complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system applies self-service by implementing automated data classification and tiering mechanisms that continuously monitor data access patterns and automatically move data between tiers without manual intervention. This self-service approach maintains storage efficiency by ensuring hot data resides in fast tiers while keeping the system manageable through automation, thereby reducing the operational complexity that would otherwise result from manual data tier management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system proactively identifies hot data and pre-loads it into faster tiers before access is needed. This preliminary action simplifies the access complexity by ensuring that frequently accessed data is already positioned in high-speed storage, reducing the need for complex real-time data movement decisions and simplifying the overall data access process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9678884B1System and method for warming cache
Publication Date: 2017.06.13 EMC IP HLDG CO LLC
  • US9678884B1 patent drawing
  • US9678884B1 patent drawing
  • US9678884B1 patent drawing

AI summary

A method, computer program product, and computing system for receiving an indication of a cold cache event within a storage system. The storage system includes a multi-tiered data array including at least a faster data tier and a slower data tier. A data list that identifies at least a portion of the data included within the faster data tier of the multi-tiered data array is obtained from the multi-tiered data array. At least a portion of the data identified within the data list is requested from the multi-tiered data array, thus defining the requested data. The requested data is received from the multi-tiered data array.