Remote Prefetch Controller for Global File System Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In a global file system with storage systems located at different geographic locations, accessing content from remote storage systems results in significantly higher latency due to network traversal, which is undesirable for users who need to access data as if it were locally stored.

Innovation Solution

Implement a dual-tier prefetch method where each storage system monitors local and remote access patterns to proactively cache anticipated future reads from remote storage systems, maintaining a predetermined number of blocks in cache to minimize latency variations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If content is accessed from remote storage systems across wide-area networks, then global file system accessibility is improved, but access latency increases significantly

Engineering Contradiction:
Improveglobal file system accessibilityVSAvoidaccess latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by detecting read patterns and prefetching content blocks from remote storage systems before they are actually requested. The controller monitors access patterns and proactively retrieves data blocks, storing them in cache memory in advance, so that when users request the content, it is already available locally, eliminating the latency penalty of remote access.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If prefetching is implemented for remote content, then access latency is reduced, but system complexity increases due to pattern monitoring and coordination

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

Solution Approach 1:

The system implements self-service by automatically detecting read patterns and initiating prefetch operations without manual intervention. The controller autonomously monitors access patterns, determines which content blocks to prefetch, and coordinates with remote storage systems, reducing the need for complex external management while maintaining intelligent prefetching functionality.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms by continuously monitoring read patterns and using this information to dynamically adjust prefetching decisions. The controller observes actual access behavior and uses this feedback to refine its predictions about which blocks will be needed next, optimizing prefetching efficiency while managing system complexity through adaptive rather than static rules.

Inventive Principle:
Principle #23Feedback

3Speed

If data blocks are cached locally, then access speed is improved, but storage resource consumption increases

Engineering Contradiction:
Improveaccess speedVSAvoidstorage resource consumption
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system applies partial action by caching only the specific data blocks that are predicted to be needed next, rather than caching entire files or directories. By detecting read patterns and prefetching only the relevant portions of content that users are likely to access soon, the system optimizes the balance between having sufficient cached data for fast access and minimizing unnecessary storage consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20250021523A1Remote prefetch
Publication Date: 2025.01.16 VAST DATA LTD
  • US20250021523A1 patent drawing
  • US20250021523A1 patent drawing
  • US20250021523A1 patent drawing

AI summary

A method for responding to access requests, the method may include (a) detecting, by a controller of a local storage system (LSS), a read pattern that (i) is associated with a requestor that is in communication with the LSS, and (ii) is estimated to comprise future read requests that are aimed to a remote part of a file system entity (FSE) that is stored at a remote storage system (RSS); wherein there is a latency difference between a remote latency associated with the remote part of the FSE and a LSS latency that is associated with the requestor; and (b) performing a prefetch process of remote sub-parts of the remote part of the FSE in order to support the read pattern while maintaining a desired latency.