Adaptive I/O Throttling for Virtual Machine Latency Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtual computing systems, resource contention issues such as 'AV storms' (simultaneous security scans) lead to substantial workloads, causing delays and performance losses, as existing resource management systems may incur performance overhead or require tedious manual coordination among virtual machines.

Innovation Solution

Implementing adaptive throttling mechanisms that monitor input/output requests, determine latency thresholds, and adjust the rate of these requests to prevent overload, allowing virtual machines to independently manage their resource usage without coordinating with others.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple virtual machines simultaneously perform security scans (AV storm), then each virtual machine can independently maintain its security functionality, but the overall system experiences substantial workload and performance degradation

Engineering Contradiction:
Improvesecurity scan functionalityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system monitors I/O latency metrics from storage operations and uses this feedback to dynamically adjust the throttling of security scan operations. When latency exceeds a threshold, the system reduces the rate of I/O requests from security applications, and when latency falls below the threshold, operations are resumed, creating a closed-loop control system that balances security needs with system performance

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically adjusts the throttling level of security scan operations based on real-time I/O latency conditions. Rather than using fixed thresholds or static rate limiting, the system continuously adapts the operation rate according to current system state, allowing security scans to proceed at full speed when resources are available and automatically slowing them down when latency indicates resource contention

Inventive Principle:
Principle #15Dynamics

2Productivity

If resource management systems attempt to mitigate performance loss through coordination mechanisms, then system performance can be improved during resource contention, but the systems incur performance overhead or require tedious manual configuration

Engineering Contradiction:
Improveperformance during resource contentionVSAvoidcoordination mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Each virtual machine is equipped with autonomous resource management capabilities that allow it to independently monitor its own I/O latency and self-regulate its security scan operations. The system does not require centralized coordination or inter-VM communication - each VM acts as its own resource manager, detecting latency conditions and adjusting its operation rate independently based on local observations and pre-configured policies

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The resource management functionality is segmented and distributed to individual virtual machines rather than being centralized. Each VM runs its own latency monitoring and throttling control logic independently, eliminating the need for complex inter-VM coordination protocols and reducing the overhead associated with centralized resource management systems

Inventive Principle:
Principle #1Segmentation

3Reliability

If the rate of input/output requests is reduced to prevent overload, then system stability is maintained, but the productivity of applications such as security scans is reduced

Engineering Contradiction:
Improvesystem stabilityVSAvoidapplication throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system uses periodic monitoring of I/O latency metrics to determine when to throttle and when to resume operations. Rather than continuously throttling or using fixed-rate limiting, the system periodically checks latency conditions and adjusts operation rates accordingly, allowing applications to proceed in bursts when conditions permit while maintaining stability through controlled pauses when latency exceeds thresholds

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9122503B1Systems and methods for adaptive throttling of input/output requests in a virtual environment
Publication Date: 2015.09.01 CA TECH INC
  • US9122503B1 patent drawing
  • US9122503B1 patent drawing
  • US9122503B1 patent drawing

AI summary

A computer-implemented method for adaptive throttling of input/output requests in a virtual environment may include (1) monitoring input/output requests sent from a virtual machine to a storage system, (2) determining a latency of one or more of the monitored input/output requests, (3) determining that the latency exceeds a threshold, and (4) reducing, in response to determining that the latency exceeds the threshold, a rate at which an application on the virtual machine sends input/output requests to the storage system. Various other methods, systems, and computer-readable media are also disclosed.