Intelligent Network Resource Manager for Database I/O Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems face challenges in managing latency-sensitive and non-latency-sensitive transactions simultaneously, as existing solutions fail to effectively utilize storage network bandwidth while meeting latency requirements for latency-sensitive Database I/O operations.

Innovation Solution

The implementation of an intelligent network resource manager that utilizes virtual channels with assigned priorities and categories on a physical communication channel, directing latency-sensitive redo log I/O messages to high-priority virtual channels and non-latency sensitive messages to lower-priority channels, ensuring efficient bandwidth allocation and minimizing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If non-latency sensitive I/O uses high network bandwidth, then bandwidth utilization is improved, but latency increases

Engineering Contradiction:
Improvenetwork bandwidth utilizationVSAvoidlatency
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent segments network traffic into multiple virtual channels with different priorities. High-priority virtual channels are dedicated to latency-sensitive redo log I/O, while lower-priority channels handle non-latency-sensitive batch and reporting I/O. This segmentation allows simultaneous optimization of both latency and bandwidth utilization without mutual interference.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different virtual channels are assigned different quality characteristics (priorities, bandwidth allocations, latency characteristics) according to the specific needs of different I/O types. Each virtual channel has tailored QoS parameters that match its intended workload, enabling localized optimization rather than uniform treatment of all traffic.

Inventive Principle:
Principle #3Local quality

2Loss of time

If redo log I/O is prioritized to reduce latency, then OLTP performance is improved, but network bandwidth for other operations is reduced

Engineering Contradiction:
Improveredo log I/O latencyVSAvoidnetwork bandwidth availability
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The network is divided into multiple virtual channels, with high-priority channels dedicated to redo log I/O and lower-priority channels for other operations. This segmentation ensures that prioritizing redo log I/O does not starve other operations of all bandwidth, as they can use the lower-priority channels.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of allocating all network bandwidth to high-priority redo log I/O, the system allocates only the necessary portion to high-priority channels while leaving remaining bandwidth available for low-priority operations. This partial action approach balances latency requirements with overall bandwidth utilization.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If virtual channels with priorities are implemented, then QoS for database I/O is improved, but device complexity increases

Engineering Contradiction:
ImproveQoS for database I/OVSAvoidnetwork resource manager complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network resource manager implements a universal virtual channel framework that handles multiple I/O types (redo log, batch, reporting) through a single prioritization mechanism. This multi-functional approach provides comprehensive QoS support without requiring separate complex management systems for each I/O type.

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

Solution Approach 2:

The system manages complexity by changing parameters (priorities, weights, bandwidth allocations) of virtual channels rather than creating fundamentally different network paths. This parameter-based QoS implementation is more manageable and less complex than structural reconfiguration approaches.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10742560B2Intelligent network resource manager
Publication Date: 2020.08.11 ORACLE INT CORP
  • US10742560B2 patent drawing
  • US10742560B2 patent drawing
  • US10742560B2 patent drawing

AI summary

A method and apparatus for intelligent network resource manager for distributed computing systems is provided. A first priority is assigned to a first virtual channel set that includes at least two virtual channels of a plurality of virtual channels associated with a physical communication channel. A second priority is assigned to a second virtual channel set that includes at least one virtual channel of the plurality of virtual channels. The first virtual channel set has more virtual channels than the second virtual channel set. Outbound messages of the first priority are directed to virtual channels of the first virtual channel set. Outbound messages of the second priority are directed to virtual channels of the second virtual channel set. The virtual channels are processed in a round-robin order, where processing includes sending the outbound messages over the physical communication channel.