Index View Pre-fetching for Document Retrieval Latency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Electronic document storage systems face latency issues in retrieval due to the need for indexing and inefficient access methods, leading to suboptimal performance in data lookup processes.

Innovation Solution

Generating index keys from extracted data values and populating an index view to automatically retrieve documents, allowing for rapid document retrieval when requested by users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If documents are indexed and stored electronically, then data storage efficiency and redundancy are improved, but retrieval latency increases

Engineering Contradiction:

Improvedata storage efficiencyVSAvoidretrieval latency

Core Design Contradiction:

Quantity of substanceVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-fetching and caching documents in the index view before they are actually requested. When index keys are populated into the index view, the corresponding documents are automatically obtained and stored in memory, so that when a user requests a document, it is already available in the cached index view, eliminating retrieval latency.

Inventive Principle:

Principle #10Preliminary action

2Speed

If index keys are generated and populated into an index view, then document retrieval speed is improved, but system complexity increases

Engineering Contradiction:

Improvedocument retrieval speedVSAvoidsystem complexity

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

The index view serves as an intermediary structure between the document storage system and the user requests. It contains index keys that map to documents, and the system automatically retrieves and caches documents in this intermediate layer. This mediator approach simplifies the retrieval process by providing a direct lookup path without requiring complex query processing for each request.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If documents are automatically obtained using index keys, then retrieval performance is improved, but memory resource consumption increases

Engineering Contradiction:

Improveretrieval performanceVSAvoidmemory resource consumption

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The system applies partial action by caching only the documents that are likely to be requested, based on the index keys populated in the index view. Rather than pre-loading all documents into memory, the system selectively obtains and caches documents corresponding to the index keys, balancing memory consumption with retrieval performance by loading only the necessary subset of documents.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS7386570B2Method, system and program product for providing high performance data lookup

Publication Date: 2008.06.10 GOOGLE LLC

AI summary

Under the present invention, index keys are generated for a set of documents. This is typically accomplished by examining the set of documents, and connecting data values extracted from the set of documents to yield the index keys. Once the index keys are generated, an index view will be generated into which the index keys are populated. Using the index keys in the index view, an agent will automatically obtain the set of documents (i.e., in the background). Then, when a user requests one of the documents, the document will already have been retrieved from storage. As such, it can readily be provided to the user. It should be understood that as used herein, the term “document” is intended to refer to any type of electronically stored data.