Virtual Storage Deferring Runtime and Interchange Formats

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing virtual storage systems face inefficiencies in managing file data sets, particularly in separating runtime and interchange formats, leading to unnecessary writes and complexities in virtual disk operations.

Innovation Solution

A virtual storage system that executes runtime activities on a runtime format file and interchange activities on an interchange format file, deferring actions until data migration, thereby avoiding unnecessary writes and simplifying virtual disk operations by separating these formats and using sparse representations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If virtual storage systems use a single format for file data sets, then administrative workflows are simpler, but runtime performance and interchange operations become less efficient due to unnecessary writes

Engineering Contradiction:

Improvestorage efficiencyVSAvoidformat management complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the file data set representation into two distinct formats: runtime format for execution activities and interchange format for data migration. This segmentation allows each format to be optimized for its specific purpose, improving storage efficiency while managing complexity through clear separation of concerns.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by using different formats in different contexts: runtime format with sparse representations for active execution, and interchange format for migration operations. This contextual adaptation optimizes performance for each specific operation type without requiring the system to maintain a single compromise format.

Inventive Principle:

Principle #3Local quality

2Productivity

If virtual storage systems execute all activities on the same file format, then file management is simpler, but redundant writes increase and performance decreases

Engineering Contradiction:

Improvevirtual disk mounting speedVSAvoidredundant write operations

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The patent performs preliminary actions by pre-processing file data sets into runtime format with sparse representations before execution activities. This preliminary preparation eliminates the need for redundant writes during runtime, as the sparse format already contains only the necessary data blocks for execution.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses copying to create sparse representations of file data sets in runtime format, copying only the necessary data blocks rather than entire files. This selective copying reduces write operations and improves mounting speed by avoiding unnecessary data transfer.

Inventive Principle:

Principle #26Copying

3Reliability

If virtual storage systems use dense file representations, then data integrity is maintained, but storage space is wasted and operations become slower

Engineering Contradiction:

Improvedata integrityVSAvoidstorage space utilization

Core Design Contradiction:

ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent applies the porous materials principle by using sparse representations that contain only the necessary data blocks with gaps for unused space. This porous structure maintains data integrity for active blocks while efficiently utilizing storage space by avoiding allocation of space for unused or deleted data.

Inventive Principle:

Principle #31Porous materials

Data Source

PatentUS10169343B2Deferring the cost of virtual storage

Publication Date: 2019.01.01 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

In one embodiment, a virtual storage system 200 may represent a file data set differently based on the activity being performed. The virtual storage system 200 may execute a runtime activity on a runtime format file 214 representing a file data set 212 on a virtual execution layer 220. The virtual storage system 200 may execute an interchange activity on an interchange format file 230 representing the file data set 232.