Cache Memory Differential Invalidation for Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cache memory systems, especially those using flash-based technology, there is a challenge in managing data arrays to ensure consistency and performance when restoring from historical records, as changes made post-generation can lead to mismatches between cache entries and data arrays, affecting overall system efficiency and cache warming times.

Innovation Solution

A method is implemented where an indication of intent to restore a data array is received, and a differential record is generated based on changes identified since the historical record's generation, allowing for the invalidation of affected data entries within the cache memory system, thereby ensuring data integrity and reducing cache warming times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cache memory systems use historical records for data array restoration, then data consistency and integrity are improved, but cache warming times increase due to changes made post-generation

Engineering Contradiction:
Improvedata consistencyVSAvoidcache warming time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system generates historical records at predetermined intervals to capture the state of data arrays before changes occur. When restoration is needed, these pre-generated records enable quick recovery without waiting for current data, reducing cache warming time while maintaining consistency through the differential record mechanism that tracks changes since the historical record was generated.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors changes to data arrays after historical records are generated and uses this feedback to create differential records. These differential records inform the invalidation process, allowing the cache to accurately reflect only the changed portions while maintaining overall consistency, thus reducing unnecessary cache warming time.

Inventive Principle:
Principle #23Feedback

2Reliability

If all data entries in cache memory are invalidated during restoration, then data integrity is ensured, but system performance decreases due to extended cache warming

Engineering Contradiction:
Improvedata integrityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of invalidating all cache entries during restoration, the system segments the data array into changed and unchanged portions using differential records. Only the changed portions are invalidated, while unchanged entries remain valid, thus maintaining system performance while ensuring data integrity for the restored portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invalidation process applies local quality by targeting only specific cache entries that correspond to changed data array portions. The differential record identifies which entries need invalidation based on actual changes, allowing selective invalidation that preserves performance while maintaining integrity where needed.

Inventive Principle:
Principle #3Local quality

3Reliability

If cache memory systems continuously track all changes to data arrays, then data consistency is maintained, but device complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidchange tracking mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the essential change information needed for consistency maintenance into differential records. Rather than tracking every detail of all changes, it captures the necessary change metadata (such as which data array portions changed and when) to inform invalidation decisions, reducing device complexity while maintaining data consistency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates copies of change information in the form of differential records that can be stored and referenced. These copies contain the essential change data needed for consistency without requiring continuous complex tracking mechanisms, allowing the system to maintain consistency by referencing historical change information rather than actively monitoring every change in real-time.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10324843B1System and method for cache management
Publication Date: 2019.06.18 EMC IP HLDG CO LLC
  • US10324843B1 patent drawing
  • US10324843B1 patent drawing
  • US10324843B1 patent drawing

AI summary

A method, computer program product, and computing system for receiving an indication of an intent to restore at least a portion of a data array based upon a historical record of the data array. One or more changes made to the content of that data array after the generation of the historical record may be identified, thus generating a differential record. One or more data entries within a cache memory system associated with the at least a portion of a data array may be invalidated based, at least in part, upon the differential record.