Compute Instance Launching Bypasses Rate Limits

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of coordinating the launch of multiple compute instances increases with the number launched, leading to challenges in resource management and overloading, necessitating more efficient methods to provide a large number of virtual machines in a short time period.

Innovation Solution

A compute instance launching system that verifies client authorization and service capacity synchronously to ensure resource availability, allowing for the parallel launch of compute instances and dynamic scaling to meet demand, while bypassing rate limits to enhance efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If multiple compute instances are launched in one request, then the number of compute instances provided increases, but the complexity of coordinating the launch increases

Engineering Contradiction:
Improvenumber of compute instancesVSAvoidcoordination complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The system segments the launch coordination into independent verification components: client authorization verification and service capacity verification. Each component handles a specific aspect of the coordination, reducing overall system complexity while enabling large-scale instance launches.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary verification of client authorization and service capacity before initiating the actual compute instance launch. This advance verification prevents coordination failures during the launch process and enables more instances to be launched simultaneously with reduced complexity.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If more compute instances are launched, then the computing resources available increase, but the risk of service overload increases

Engineering Contradiction:
Improvecomputing resourcesVSAvoidservice stability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary capacity verification to determine whether sufficient resources are available before launching compute instances. This advance check prevents service overload by ensuring that the total number of instances being launched does not exceed available capacity, thereby maintaining service stability while maximizing resource utilization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses capacity verification feedback to dynamically adjust launch decisions. By continuously monitoring available capacity and using this information to control instance launches, the system prevents overload conditions while maximizing the number of instances that can be safely launched.

Inventive Principle:
Principle #23Feedback

3Loss of time

If traditional sequential launch methods are used, then resource coordination is simplified, but the launch time increases

Engineering Contradiction:
Improvelaunch timeVSAvoidlaunch efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The system performs authorization and capacity verification in advance, before the actual instance launch begins. This preliminary action separates the verification phase from the launch phase, allowing instances to be launched in parallel without sequential coordination delays, thereby reducing total launch time while maintaining resource coordination safety.

Inventive Principle:
Principle #10Preliminary action

4Speed

If rate limits are enforced during instance launch, then service overload is prevented, but the launch speed decreases

Engineering Contradiction:
Improveinstance launch speedVSAvoidresource management safety
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system enforces rate limits during the preliminary verification phase rather than during the actual instance launch. By checking authorization and capacity in advance and approving the entire batch upfront, the system allows all approved instances to launch in parallel at maximum speed without being throttled by rate limits during the launch itself, thereby maintaining both safety and speed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10761875B1Large scale compute instance launching
Publication Date: 2020.09.01 AMAZON TECH INC
  • US10761875B1 patent drawing
  • US10761875B1 patent drawing
  • US10761875B1 patent drawing

AI summary

A method for launching a plurality of computing instances may include obtaining a request to launch a plurality of computing instances. The request may indicate a first number and a target number of compute instances that is larger than the first number. The method may further include verifying that there is sufficient capacity, for example of a compute instance service, to launch at least the first number of compute instances. The request may be fulfilled by at least launching at least the first number of compute instances in a way that bypasses a rate limit that limits a rate at which compute instances can be launched. In some cases, the method may additionally include launching additional compute instances, as they become available, until the target number has been reached.