Preemptive Data Extraction from Long Latency Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud computing environments, data stored in long latency storage takes a long time to retrieve due to the need to power on hosting machines, resulting in high costs for customers, as they pay a premium for resource utilization during data retrieval.

Innovation Solution

A resource utilization mechanism (RUM) identifies periods of low resource utilization to preemptively extract data from long latency storage and move it to low latency storage, making it available to customers before request, while notifying them of availability and allowing them to accept or opt out of using the data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If data is stored in long latency storage to reduce costs, then storage cost is reduced, but data retrieval time increases significantly

Engineering Contradiction:
Improvestorage costVSAvoiddata retrieval time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The system performs preliminary actions by identifying and extracting data from long latency storage during periods of low resource utilization, before the customer actually requests the data. This proactive approach prepares data in advance, so when retrieval is needed, the data is already available in low latency storage, eliminating the long wait time while still benefiting from cost-effective long latency storage.

Inventive Principle:
Principle #10Preliminary action

2Speed

If data is extracted from long latency storage during low utilization periods, then data retrieval speed improves, but resource utilization complexity increases

Engineering Contradiction:
Improvedata retrieval speedVSAvoidresource utilization complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The resource utilization mechanism operates autonomously to identify low utilization periods and automatically extract appropriate data without requiring complex manual intervention. The system monitors resource utilization patterns, makes intelligent decisions about which data to extract, and executes the extraction process automatically, thereby managing complexity internally while presenting a simple interface to customers.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If hosting machines are powered on to retrieve long latency data, then data becomes accessible, but energy consumption and costs increase

Engineering Contradiction:
Improvedata accessibilityVSAvoidenergy consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

Data is extracted and transferred to low latency storage during periods of low resource utilization, preparing it in advance for future access. This preliminary action ensures that when data retrieval is actually needed, the hosting machines are already powered on and the data is readily accessible, eliminating the need to power on machines specifically for retrieval operations and thus reducing energy consumption.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10057332B2Preemptive extraction of data from long latency storage in a cloud computing environment
Publication Date: 2018.08.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10057332B2 patent drawing
  • US10057332B2 patent drawing
  • US10057332B2 patent drawing

AI summary

A resource utilization mechanism (RUM) preemptively extracts data from long latency storage in a cloud computing environment to economically and quickly provide data that is infrequently accessed by customers. The RUM identifies periods of low resource utilization where capacity can be efficiently utilized, identifies data to be retrieved, and retrieves the data from long latency storage to make it available to the customer. The RUM may notify a customer that the data is available and allow the customer to accept terms of use for the data or opt out of using the data.