Intelligent Resource Autostopping for Cloud Cost Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing service providers charge customers for resources even when they are idle, leading to unnecessary costs.

Innovation Solution

An intelligent shutdown system that detects idle resources and shuts them down based on configured rules, redirecting traffic to a proxy machine and restarting resources as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If resources are kept running continuously to ensure immediate availability, then service reliability is improved, but resource cost increases due to charging for idle time

Engineering Contradiction:
Improveservice availabilityVSAvoidresource cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system dynamically adjusts resource states between running and stopped based on real-time traffic conditions. Resources are kept running when traffic is detected and stopped when idle, creating a dynamic adaptation to workload demands rather than static continuous operation

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

A proxy machine serves as an intermediary between clients and backend resources. When resources are stopped, the proxy machine receives client requests and forwards them to the resource group, enabling seamless traffic redirection without requiring resources to remain continuously running

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of energy

If resources are stopped to reduce costs during idle periods, then resource cost decreases, but service availability deteriorates until resources are restarted

Engineering Contradiction:
Improveresource costVSAvoidservice availability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-warming resource groups before traffic arrives. When traffic is detected at the proxy machine, the system proactively starts the resource group in advance, ensuring resources are ready before actual service demands occur

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by monitoring traffic patterns and using this information to automatically control resource states. The proxy machine detects traffic and sends feedback signals to start or stop resource groups, creating a closed-loop control system that adapts to actual usage patterns

Inventive Principle:
Principle #23Feedback

3Loss of energy

If traffic redirection to proxy machine is implemented when resources are stopped, then resource cost is reduced, but system complexity increases due to additional traffic management logic

Engineering Contradiction:
Improveresource costVSAvoidtraffic management complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The proxy machine acts as a simplified intermediary that handles all traffic management logic centrally. Rather than implementing complex logic in each resource or client, the proxy machine provides a single point of control for traffic redirection, resource state management, and coordination

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The proxy machine performs multiple functions including traffic reception, resource state monitoring, automatic resource group management, and client communication. This multi-functional design consolidates complexity into a single component rather than distributing it across multiple systems

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12299486B2Intelligent autostopping of resources in computing environments
Publication Date: 2025.05.13 HARNESS INC
  • US12299486B2 patent drawing
  • US12299486B2 patent drawing
  • US12299486B2 patent drawing

AI summary

A system that provides intelligent shutdown of a resource when the resource is idle for a set period of time. A set of rules may be configured to determine when to shut down the resource, in what order, how to handle traffic when a resource is shut down, and how to startup resources that have been previously shut down when demand requires it. In addition to setting an idle time at which point to shut down the resource, the type of shutdown may be configured. Dependencies may be configured, which indicate how the resource should be shut down or powered up with respect to other resources. A user interface may be used to configure rules, and a dashboard may be provided to see the current status and cost savings information for a set of resources for a system.