Peer-to-Peer Collaborative Caching for Storage Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed storage systems face high latency and access time issues due to reliance on slower central servers and disk arrays for data retrieval, especially when data is geographically distant.

Innovation Solution

Implementing peer-to-peer collaborative caching, where peers maintain a distributed cache and simultaneously query multiple remote locations, including local disks and origin or database servers, to reduce latency by estimating and optimizing data retrieval from various sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is retrieved from central servers or remote databases, then data availability is ensured, but access time increases significantly

Engineering Contradiction:
Improvedata availabilityVSAvoidaccess time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments data retrieval by querying multiple remote locations simultaneously (different peers, caches, disks) rather than relying on a single central server. This parallel segmentation of retrieval paths reduces access time while maintaining data availability through any successful retrieval path.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-establishing a list of remote locations where data may be stored and by proactively caching data at multiple locations before it is needed. When data is requested, the system already has a prepared list of potential sources, enabling immediate parallel retrieval without waiting for sequential queries.

Inventive Principle:
Principle #10Preliminary action

2Speed

If multiple remote locations are queried simultaneously, then data retrieval speed increases, but system complexity increases

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

Solution Approach 1:

Each peer automatically manages its own data retrieval process by maintaining a local list of remote locations and autonomously determining which locations to query. The system is self-organizing, with peers independently tracking data locations and initiating parallel queries without requiring centralized coordination, thus managing complexity at the individual peer level rather than system-wide.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-maintaining a list of remote locations at each peer before data retrieval is needed. This pre-established inventory allows immediate parallel querying without complex real-time discovery processes, reducing operational complexity while enabling fast multi-location retrieval.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If data is cached at multiple locations, then access time decreases, but storage requirements increase

Engineering Contradiction:
Improveaccess timeVSAvoidstorage requirements
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The system applies local quality by having each peer cache only the data it needs based on its specific access patterns and the list of remote locations it maintains. Rather than uniform caching across the entire system, each peer customizes its local cache according to its operational requirements, reducing overall storage consumption while maintaining fast access for frequently needed data.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system uses partial action by querying and caching data at only the necessary remote locations rather than all possible locations. The peer maintains a selective list of remote locations based on data availability and accessibility, performing partial retrieval operations that balance storage requirements with access speed benefits.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9292620B1Retrieving data from multiple locations in storage systems
Publication Date: 2016.03.22 HEWLETT PACKARD ENTERPRISE DEV LP
  • US9292620B1 patent drawing
  • US9292620B1 patent drawing
  • US9292620B1 patent drawing

AI summary

Embodiments include methods, apparatus, and systems for retrieving data from multiple locations in storage systems. One embodiment includes a method that determines that data is stored in multiple locations remote to a computer, estimates a latency to retrieve the data from the multiple locations, and requests the data from the plural locations.