Layer-aware data movement control for container images

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing access to container images in dense cloud infrastructure deployments is challenging due to inefficiencies in data movement control, particularly in handling large numbers of container images with complex layer structures.

Innovation Solution

Implementing layer-aware data movement control by assigning prefetching and cache-swapping priority weights to different layers of container images, using separate LRU or LFU lists for each layer, and dynamically adjusting these weights based on layer structure changes to optimize data access and storage efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If container images are stored in a unified storage pool without layer-aware control, then storage management is simplified, but data access efficiency deteriorates due to inability to differentiate between frequently accessed layers and less important layers

Engineering Contradiction:
Improvestorage management simplicityVSAvoiddata access efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent segments container image storage into distinct layer structures (read-only layers and read-write layers) with different storage policies. Each layer type is managed separately with dedicated storage devices and data movement control, allowing optimized access patterns for each segment while maintaining overall storage organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different storage qualities and access policies to different parts of the container image structure. Read-only layers use aggressive caching and prefetching with higher priority data movement, while read-write layers use more conservative policies. This local differentiation optimizes overall system performance without requiring complete redesign of storage management.

Inventive Principle:
Principle #3Local quality

2Device complexity

If data movement control treats all container layers uniformly, then control logic is simpler, but performance deteriorates due to inability to prioritize frequently accessed layers

Engineering Contradiction:
Improvecontrol logic complexityVSAvoiddata access speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The patent implements dynamic data movement control that adapts to changing container layer characteristics. The system monitors layer usage patterns and adjusts prefetching priorities, cache replacement policies, and data movement timing based on real-time conditions, allowing the control logic to respond to workload changes while maintaining performance optimization.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent employs prefetching mechanisms that proactively load container layer data into cache before it is actually needed. By analyzing layer dependencies and access patterns, the system预先 loads read-only layers and anticipates read-write layer access requirements, reducing actual data access latency without requiring complex real-time control during critical operations.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If cache memory is shared across all container layers without layer-aware policies, then memory utilization is maximized, but access efficiency deteriorates due to inability to prioritize critical layers

Engineering Contradiction:
Improvememory utilizationVSAvoidaccess efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent segments cache memory allocation by layer type, providing dedicated cache spaces for read-only layers and read-write layers. This segmentation allows each layer type to have optimized cache policies while collectively utilizing available memory resources efficiently, preventing cache conflicts between different layer access patterns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent dynamically changes cache management parameters based on layer characteristics. Read-only layers receive higher prefetching priorities and more aggressive cache replacement policies, while read-write layers use more conservative approaches. These parameter adjustments optimize cache utilization for each layer type without requiring separate physical memory allocations.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If prefetching is applied uniformly to all container data, then data availability is improved, but resource waste increases due to prefetching unnecessary data

Engineering Contradiction:
Improvedata availabilityVSAvoidresource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies prefetching selectively based on layer characteristics and access patterns. Read-only layers with high read throughput requirements receive aggressive prefetching, while read-write layers with unpredictable access patterns use more conservative approaches. This localized prefetching strategy ensures data availability where needed while minimizing unnecessary data movement and resource consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements feedback mechanisms that monitor actual layer access patterns and adjust prefetching behavior accordingly. When prefetching proves unnecessary or ineffective for certain layers, the system reduces or eliminates prefetching for those specific cases, optimizing resource utilization while maintaining data availability for layers that benefit from proactive loading.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10659533B1Layer-aware data movement control for containers
Publication Date: 2020.05.19 EMC IP HLDG CO LLC
  • US10659533B1 patent drawing
  • US10659533B1 patent drawing
  • US10659533B1 patent drawing

AI summary

An apparatus in one embodiment comprises a plurality of container host devices of at least one processing platform. The container host devices implement a plurality of containers for executing applications on behalf of one or more tenants of cloud infrastructure. The containers have associated layer structures each characterizing container images of respective different ones of the containers. Movement of container data between different storage devices by at least one of the container host devices for at least one of the containers is controlled based at least in part on one or more characteristics of a corresponding one of the layer structures. For example, controlling movement of container data between the different storage devices may comprise assigning at least one of different prefetching priority weights and different cache-swapping priority weights to different layers of the given layer structure.