Load Balancing Oscillation Prevention via State-Space Modeling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing load balancing techniques in multi-node distributed systems often lead to oscillatory behavior, resulting in inefficient operation and degraded performance, as they fail to generalize well under changing conditions and often improperly treat normal dynamic behavior as oscillatory.

Innovation Solution

A system that uses load-balancing policies to distribute requests across nodes, determining operational characteristics to compute machine queuing models and fit a state-space model, allowing for dynamic detection and prevention of oscillatory behavior by adjusting tunable parameters or switching to a different policy if necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If load-balancing techniques are used to distribute requests across nodes, then request distribution is achieved, but oscillatory behavior occurs leading to degraded performance

Engineering Contradiction:
Improverequest distribution efficiencyVSAvoidsystem performance stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism that continuously monitors system state and adjusts load-balancing decisions dynamically. The load manager observes node states and modifies request distribution accordingly, creating a closed-loop control system that prevents oscillatory behavior by responding to actual system conditions rather than following fixed patterns

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent transitions from static load-balancing rules to dynamic adaptation. The system continuously adjusts load-balancing parameters based on real-time observations of node states, request patterns, and system conditions. This dynamic approach allows the system to adapt to changing conditions without exhibiting oscillatory behavior that plagues static approaches

Inventive Principle:
Principle #15Dynamics

2Reliability

If heuristic techniques are used to reduce oscillation, then oscillation reduction is achieved, but the techniques fail to generalize under changing operational conditions

Engineering Contradiction:
Improveoscillation reductionVSAvoidgeneralization under changing conditions
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent dynamically changes load-balancing parameters based on observed system conditions rather than using fixed heuristics. The system monitors operational characteristics and adjusts parameters such as request distribution weights, thresholds, and timing accordingly. This parameter adaptation allows the system to maintain effectiveness across diverse and changing operational conditions

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent creates a universal load-balancing framework that can handle multiple types of workloads and system configurations through a single adaptive mechanism. Rather than requiring different heuristics for different conditions, the system uses a unified approach that observes system state and adapts accordingly, making it versatile across changing operational scenarios

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

Data Source

PatentUS9448849B2Preventing oscillatory load behavior in a multi-node distributed system
Publication Date: 2016.09.20 ORACLE INT CORP
  • US9448849B2 patent drawing
  • US9448849B2 patent drawing
  • US9448849B2 patent drawing

AI summary

The disclosed embodiments provide a system that prevents oscillatory load behavior for a multi-node distributed system. During operation, the system uses a load-balancing policy to distribute requests to nodes of the distributed system. The system determines operational characteristics for the nodes as they process a set of requests, and then uses these operational characteristics to compute machine queuing models that describe the machine state of each node. The system then uses this machine state for the nodes to determine whether the load-balancing policy and the distributed system are susceptible to oscillatory load behavior.