Intelligent Load Shedding via Real-Time Scaling Unit Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional load shedding techniques in computing systems are inefficient as they shed traffic without knowledge of the current resource utilization of scaling units, leading to inefficient routing and potential overload.

Innovation Solution

Implementing an intelligent load shedding system where each scaling unit publishes its load characteristics, allowing for intelligent routing decisions to be made based on current resource utilization, with traffic routed to locations not critically loaded, and proactive assistance sought from neighboring locations to avoid overload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If traditional load shedding techniques are used to shed traffic without knowledge of current resource utilization, then traffic can be shed quickly, but routing efficiency deteriorates and potential overload occurs

Engineering Contradiction:
Improvetraffic shedding speedVSAvoidrouting efficiency
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The system implements feedback by having scaling units publish their current load state to a central entity, which then uses this information to make intelligent routing decisions. This feedback loop enables the system to route traffic based on real-time resource utilization, preventing overload while maintaining routing efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary action by proactively seeking assistance from neighboring locations before overload occurs. The intelligent routing system uses current load state information to predict potential bottlenecks and redirect traffic in advance, preventing overload conditions rather than reacting after they occur.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If traffic is routed without knowledge of current load state, then routing decisions are simpler, but system reliability deteriorates due to potential overload

Engineering Contradiction:
Improverouting decision complexityVSAvoidsystem reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system implements feedback by having scaling units publish their current load state to a central entity, which then uses this information to make intelligent routing decisions. This feedback loop enables the system to route traffic based on real-time resource utilization, preventing overload while maintaining routing efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system introduces an intermediary component that acts as a central entity to collect load state information from scaling units and make routing decisions. This intermediary simplifies the complexity by centralizing the intelligence, allowing individual scaling units to remain simple while the system as a whole achieves high reliability through informed routing decisions.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If intelligent routing based on current load state is implemented, then routing efficiency improves, but system complexity increases

Engineering Contradiction:
Improverouting efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary component that acts as a central entity to collect load state information from scaling units and make routing decisions. This intermediary simplifies the complexity by centralizing the intelligence, allowing individual scaling units to remain simple while the system as a whole achieves high reliability through informed routing decisions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service by having scaling units autonomously publish their own load state information to the central entity. This eliminates the need for complex monitoring infrastructure, as each unit independently contributes to the collective intelligence of the system, maintaining routing efficiency while minimizing added complexity.

Inventive Principle:
Principle #25Self-service

4Speed

If load shedding is performed without knowledge of target capacity, then traffic can be shed rapidly, but loss of information occurs regarding resource utilization

Engineering Contradiction:
Improveload shedding speedVSAvoidresource utilization information
Core Design Contradiction:
SpeedVSLoss of information

Solution Approach 1:

The system implements feedback by having scaling units publish their current load state to a central entity, which then uses this information to make intelligent routing decisions. This feedback loop enables the system to route traffic based on real-time resource utilization, preventing overload while maintaining routing efficiency.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3685567B1Load shedding of traffic based on current load state of target capacity
Publication Date: 2021.07.21 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3685567B1 patent drawingFigure 1
  • EP3685567B1 patent drawingFigure 2
  • EP3685567B1 patent drawingFigure 3

AI summary

Various embodiments of the present technology generally relate to systems and methods for intelligent load shedding. More specifically, various embodiments of the present technology generally relate to intelligent load shedding of traffic based on current load state of target capacity. In some embodiments, a domain name resolution request to translate a domain name into an Internet protocol (IP) address can be received at DNS server. A status of each of multiple scaling units mapped to the domain name can be determined. A set of IP addresses (e.g., four IP addresses) corresponding to a subset of the multiple scaling units closest to the requesting device with statuses indicating availability for new traffic can be identified. Then, the set of IP addresses can be sent to the requesting device. The requesting device can the select which IP address to use (e.g., randomly) to route the traffic.