Client-configurable ML resource retention periods

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing machine learning services face significant overhead in configuring and preparing computing resources for each machine learning task, which can lead to delays and increased costs.

Innovation Solution

Implementing client-specified post-task-completion retention periods for computing resources allows for the re-use of resources for subsequent tasks, reducing the need for repeated configuration and setup.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If computing resources are re-configured for each machine learning task, then resource utilization efficiency is improved, but task execution delay increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidtask execution delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by retaining computing resources in a warm state after task completion, pre-configuring them for potential future tasks. This allows resources to be immediately available for subsequent tasks without requiring full reconfiguration, thus reducing task execution delay while maintaining good resource utilization efficiency.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If computing resources are retained after task completion, then resource re-use efficiency is improved, but resource cost increases

Engineering Contradiction:
Improveresource re-use efficiencyVSAvoidresource cost
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system dynamically adjusts resource retention based on demand. Resources are retained in a warm state only when there is pending or potential demand for similar tasks, and are released when no longer needed. This dynamic approach improves resource re-use efficiency by keeping resources available for quick re-deployment while controlling costs by releasing resources that are not being utilized.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the state parameter of computing resources from fully deactivated to a warm retained state. This intermediate state allows resources to maintain certain configurations and data in memory without full operational overhead, enabling faster re-use while reducing the cost compared to fully active resources.

Inventive Principle:
Principle #35Parameter changes

3Speed

If computing resources are fully configured for each task, then task execution speed is improved, but configuration overhead increases

Engineering Contradiction:
Improvetask execution speedVSAvoidconfiguration overhead
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system performs preliminary configuration actions by maintaining resources in a warm state with pre-loaded configurations and data. When a new task arrives, the resource is already partially configured, eliminating the need for full reconfiguration and enabling faster task execution while reducing configuration overhead.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If computing resources are immediately released after task completion, then resource availability for other tasks is improved, but startup overhead for subsequent tasks increases

Engineering Contradiction:
Improveresource availabilityVSAvoidstartup overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by retaining resources in a warm state rather than immediately releasing them. This allows resources to be quickly re-deployed to subsequent tasks with minimal startup overhead, while still maintaining availability through controlled retention policies that ensure resources are released when no longer needed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250181409A1Client-configurable retention periods for machine learning service-managed resources
Publication Date: 2025.06.05 AMAZON TECH INC
  • US20250181409A1 patent drawing
  • US20250181409A1 patent drawing
  • US20250181409A1 patent drawing

AI summary

A post-task-completion retention period for which a computing resource is to be retained, without de-activating the resource, on behalf of a set of requesters of machine learning tasks is determined at a machine learning service. A first task, identified at the service prior to expiration of the retention period at a first computing resource at which a second task has completed, is initiated at the first computing resource. In response to obtaining an indication of a third task and determining that a threshold criterion associated with the retention period satisfies a criterion, the third task is initiated at an additional computing resource. The additional computing resource is de-activated after the third task completes, without waiting for the retention period to expire.