Virtualization Resource Ratio Scaling for Application Bottlenecks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for scaling virtualization containers in applications often lead to suboptimal operation and inefficient resource usage, as adding additional resources can create bottlenecks and fail to improve performance significantly, especially when not all layers of virtualization containers are scaled proportionally.

Innovation Solution

The approach involves using a resource ratio to scale virtualization containers, where each layer of an application is scaled to a multiple of its initial ratio, ensuring that all layers process data efficiently and preventing bottlenecks by allocating additional resources based on available surplus resources and specific application needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If additional virtualization containers are added to an application layer, then the application's processing capacity increases, but resource allocation becomes inefficient and bottlenecks occur when layers are not scaled proportionally

Engineering Contradiction:
Improveapplication processing capacityVSAvoidresource allocation efficiency
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent applies parameter changes by dynamically adjusting the number of virtualization containers in each layer based on a resource ratio. When scaling an application, the system calculates the appropriate multiple for each layer's container count according to its designated ratio, ensuring proportional scaling across all layers. This prevents resource allocation inefficiency and bottlenecks by maintaining balanced capacity distribution while improving overall processing capacity.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If virtualization containers are scaled without considering resource ratios, then deployment is simpler, but performance optimization is suboptimal and bottlenecks occur

Engineering Contradiction:
Improvedeployment simplicityVSAvoidapplication performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements preliminary action by pre-defining resource ratios for each layer of the application during the deployment configuration stage. These ratios are established in advance based on the specific performance requirements and characteristics of each layer. When scaling occurs later, the system simply applies the predetermined ratios to calculate the appropriate container counts, maintaining both deployment simplicity and performance optimization without requiring complex real-time adjustments.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If resources are allocated based on available surplus without considering application needs, then resource utilization improves, but application-specific performance requirements are not met

Engineering Contradiction:
Improveresource utilizationVSAvoidapplication performance guarantee
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent applies local quality by allocating resources according to the specific needs and characteristics of each application layer. Each layer is assigned a resource ratio that reflects its particular performance requirements and workload characteristics. When surplus resources are available, the system distributes them to layers based on their individual ratios rather than uniformly, ensuring that each layer receives appropriate resources to meet its specific performance guarantees while improving overall resource utilization.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12164970B2Scaling virtualization resource units of applications
Publication Date: 2024.12.10 COHESITY INC
  • US12164970B2 patent drawing
  • US12164970B2 patent drawing
  • US12164970B2 patent drawing

AI summary

A request to launch an application that is comprised of a plurality of layers is received. Each layer of the plurality of layers of the application is comprised of one or more corresponding virtualization resource units. The one or more corresponding virtualization resource units at each of the plurality of layers of the application is expressed as a resource ratio. It is determined that a surplus of resources is available for one or more applications. In response to determining that the surplus of resources is available for one or more applications, a priority associated with the application is determined. A version of the application is launched based on the determined priority associated with the application. The launched version of the application maintains the resource ratio.