Two-Layer Cloud Cache with Boot Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems interfacing with cloud storage face challenges in efficiently caching frequently used data to enhance access speed, particularly in enterprise systems, where HDDs offer large capacity but slow data access, and SSDs provide fast access but at a higher cost.

Innovation Solution

A caching system with two layers - a filter for analyzing read access patterns and a cache memory comprising a main cache and a boot cache, where the boot cache is used during system startup and partially cleared for new data, and the main cache has no specific data limits, with a persistent design using SSDs for faster data access and metadata storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is cached in SSD to improve data access speed, then access speed is improved, but storage capacity is reduced and cost increases

Engineering Contradiction:
Improvedata access speedVSAvoidstorage capacity
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The caching system is divided into two distinct segments: a boot cache for temporary startup data and a main cache for persistent frequently accessed data. This segmentation allows the system to manage different data types with different retention policies, optimizing both speed and capacity utilization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The boot cache is dynamically cleared after system startup, transitioning from a temporary caching state to a main cache state. This dynamic behavior allows the system to adapt cache usage based on operational phase, ensuring fast access during startup while maintaining capacity for persistent data.

Inventive Principle:
Principle #15Dynamics

2Quantity of substance

If boot cache is cleared to make space for new data, then storage capacity is improved, but data loss occurs

Engineering Contradiction:
Improvestorage capacityVSAvoiddata loss
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The boot cache is extracted as a separate, temporary caching layer that is intentionally cleared after startup. This extraction allows the system to discard transient startup data while preserving important data in the main cache, preventing loss of critical information.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Different quality characteristics are applied to different cache regions: the boot cache is temporary and disposable, while the main cache maintains persistent storage quality. This local differentiation ensures that data loss in the boot cache does not affect important stored data.

Inventive Principle:
Principle #3Local quality

3Speed

If cache memory is increased to store more data, then data access speed is improved, but system complexity increases

Engineering Contradiction:
Improvedata access speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The cache memory is segmented into boot cache and main cache with distinct functions and management policies. This segmentation simplifies the overall system by providing clear separation of concerns, making each cache region easier to manage and optimize independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The caching system operates autonomously by automatically managing boot cache clearance and main cache population based on system state. This self-service mechanism reduces the need for complex external control and monitoring systems.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9678880B1System and method for cache management in systems that interface to cloud storage
Publication Date: 2017.06.13 VIRTUOZZO INT GMBH
  • US9678880B1 patent drawing
  • US9678880B1 patent drawing
  • US9678880B1 patent drawing

AI summary

A method and a system for cache management in system interfacing to a cloud storage. The cache has two layers: the filter layer for tracing read access to the data blocks and the cache layer for keeping the actual data blocks. The layer two consists of two modules—a main cache and a boot cache. The boot cache is filled during the short period of time after the first file open operation. The boot cache also has a limit on the amount of data that can be put into the cache for the particular file. The filter layer detects continuous read access pattern and avoids caching data, if the data is read continuously beyond some limit.