Workload Management System for Database Resource Allocation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Database management systems face challenges in managing diverse workloads with varying resource demands and execution times, particularly in handling complex queries and new data types, which requires dynamic adjustment of resources to meet performance goals for multiple workloads simultaneously.

Innovation Solution

A method and system for mapping business concepts to database feature settings, using rules and workload definitions to filter, throttle, and prioritize requests, allowing for dynamic resource allocation and adjustment based on business requirements, enabling effective management of complex multi-class workloads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dynamic resource allocation is implemented to meet performance goals for multiple workloads, then system performance is improved, but device complexity increases

Engineering Contradiction:

Improvesystem performanceVSAvoidworkload management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments workloads into distinct classes (OLTP, OLAP, OLM, OLX) with different resource requirements and performance goals. Each workload class is managed separately through dedicated parameters and settings, allowing the system to handle diverse workloads without overwhelming complexity in the management layer.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system implements dynamic resource allocation by allowing real-time adjustment of workload parameters, priority levels, and resource assignments based on current system conditions and workload characteristics. This enables the system to adapt to changing performance goals while managing complexity through automated dynamic decision-making.

Inventive Principle:

Principle #15Dynamics

2Ease of operation

If filtering rules are applied to reject requests, then workload management is simplified, but loss of information increases

Engineering Contradiction:

Improveworkload management simplicityVSAvoidrequest rejection

Core Design Contradiction:

Ease of operationVSLoss of information

Solution Approach 1:

The patent introduces an intermediary layer of workload management that sits between request submission and execution. This intermediary layer applies filtering rules and workload classifications to manage requests, providing a structured approach to decision-making while maintaining transparency through detailed logging and monitoring of filtered requests.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Stability of the object's composition

If throttling rules are applied to delay requests, then system stability is improved, but loss of time increases

Engineering Contradiction:

Improvesystem stabilityVSAvoidrequest delay

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system implements periodic review and adjustment of throttling parameters based on workload patterns and system conditions. By evaluating throttling effectiveness over time and adjusting rules periodically, the system maintains stability while minimizing unnecessary delays through adaptive throttling strategies.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS7693847B1Administering workload groups

Publication Date: 2010.04.06 TERADATA US INC

AI summary

A method, system and computer program for mapping business concepts related to the processing of requests on a database system to database system feature settings is disclosed. Rules limit the requests that will be submitted to the database system for processing and establish workload definitions that can be used to map each request submitted to the database system for processing to database feature settings, based on business concepts associated with each request.