Serverless Workload Prediction for Proactive Container Pre-Warming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current serverless computing platforms face performance degradation due to naive, threshold-based auto-scaling approaches that lead to wasted resources and inefficiencies, particularly under interactive and bursty workloads, and neglect replica start-up latency, resulting in SLA violations and cold start latency issues.

Innovation Solution

A proactive auto-scaling method using workload prediction and control-theoretic resource orchestration, which predicts future workloads and adjusts resources in advance to meet performance metrics, employing machine learning and fake requests to optimize resource usage and reduce latency in both private and public cloud environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If threshold-based auto-scaling is used to manage serverless workloads, then resource allocation is simplified, but performance degrades due to wasted resources and inefficiencies

Engineering Contradiction:
Improveresource allocation complexityVSAvoidworkload processing efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system performs preliminary actions by predicting future workloads using machine learning models before they actually occur. This allows the auto-scaling system to pre-provision resources in advance, avoiding the reactive delays of threshold-based approaches and ensuring resources are ready when needed, thus improving efficiency without excessive complexity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring actual workload performance and using this data to refine predictions and adjust resource allocation. This closed-loop approach optimizes resource efficiency dynamically while maintaining manageable system complexity through automated adaptation

Inventive Principle:
Principle #23Feedback

2Ease of operation

If predefined threshold-based orchestration is used, then system operation is simplified, but SLA violations occur due to inability to handle bursty workloads

Engineering Contradiction:
Improveorchestration simplicityVSAvoidSLA compliance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary scaling actions based on predicted workload trends before SLA violations can occur. By anticipating bursty workloads through machine learning predictions, the system proactively provisions resources in advance, maintaining SLA compliance while keeping orchestration logic simplified through automated prediction-driven decisions

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system transitions from static threshold-based orchestration to dynamic prediction-driven orchestration. The auto-scaling behavior adapts continuously to changing workload patterns, enabling the system to handle bursty workloads reliably while maintaining operational simplicity through automated dynamic adjustment

Inventive Principle:
Principle #15Dynamics

3Loss of energy

If resources are scaled down to reduce costs, then resource efficiency improves, but cold start latency increases

Engineering Contradiction:
Improveresource consumptionVSAvoidcold start latency
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The system performs preliminary resource provisioning based on predicted workload patterns. By anticipating future demand, the system keeps resources in a warm state before they are actually needed, reducing cold start latency while avoiding the continuous resource consumption of always-on approaches, thus optimizing the trade-off between resource efficiency and response time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically changes resource provisioning parameters based on predicted workload characteristics. Instead of fixed scaling policies, the system adjusts resource states (provisioned, warmed, or scaled down) according to prediction confidence and workload patterns, optimizing the balance between resource consumption and cold start latency

Inventive Principle:
Principle #35Parameter changes

4Speed

If proactive resource scaling is implemented, then response times improve, but system complexity increases

Engineering Contradiction:
Improveresponse timeVSAvoidsystem architecture complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system introduces machine learning prediction models as intermediary components between workload demands and resource provisioning. These intermediaries translate complex prediction algorithms into actionable scaling decisions, improving response times while managing system complexity by encapsulating the intelligence in separate prediction modules rather than distributed across the entire system

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11394621B2Proactively accomodating predicted future serverless workloads using a machine learning prediction model
Publication Date: 2022.07.19 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11394621B2 patent drawing
  • US11394621B2 patent drawing
  • US11394621B2 patent drawing

AI summary

Example implementations relate to a proactive auto-scaling approach. According to an example, a machine-learning prediction model is trained to forecast future serverless workloads during a window of time for an application running in a public cloud based on past serverless workload information associated with the application by performing a training process. During the window of time, serverless workload information associated with the application is monitored. A future serverless workload is predicted for the application at a future time within the window, based on the machine learning prediction model. Prior to the future time, containers within the public cloud executing the application are pre-warmed to accommodate the predicted future serverless workload by issuing fake requests to the application to trigger auto-scaling functionality implemented by the public cloud.