Database Request Container Allocation via Predictive Models

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems face inefficiencies in processing large volumes of database requests due to inadequate dynamic resource allocation and processing capacity, leading to inefficiencies in computational processing and increased complexity in tracking transaction confirmations or failures.

Innovation Solution

A container management system that dynamically allocates data containers and processor resources based on real-time request rates using predictive models and meta-data sorting, coupled with a processor hosting service for scalable processing, and utilizes blockchain for secure transaction logging.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If dynamic resource allocation is implemented, then processing capacity and computational efficiency are improved, but system complexity increases

Engineering Contradiction:
Improveprocessing capacityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system dynamically allocates computing resources by adjusting the number and size of data containers based on real-time request rates. The container management system continuously monitors incoming database requests and modifies resource allocation accordingly, transforming a static system into a dynamic one that adapts to varying workloads, thereby improving processing capacity without requiring permanent over-provisioning of resources.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The container management system autonomously manages resource allocation without requiring external intervention. It automatically calculates receiving rates, determines optimal container configurations using predictive models, and adjusts data container allocations based on current system state. This self-service capability handles the complexity internally while presenting a simplified interface to users and applications.

Inventive Principle:
Principle #25Self-service

2Productivity

If predictive models are used for resource allocation, then resource utilization efficiency is improved, but computational overhead increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidcomputational overhead
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system applies predictive models selectively rather than continuously. It calculates receiving rates at appropriate intervals and uses predictive models only when needed to determine container allocations, rather than constantly predicting and adjusting. This partial application of predictive analytics improves resource utilization efficiency while avoiding the excessive computational overhead of continuous prediction cycles.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The predictive model serves multiple functions: it estimates future request rates, determines optimal container configurations, and guides resource allocation decisions. By making the predictive model multi-functional, the system achieves improved resource utilization efficiency without requiring separate computational mechanisms for each function, thereby reducing overall computational overhead.

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

3Speed

If data containers are dynamically allocated and transferred, then processing speed is improved, but memory management complexity increases

Engineering Contradiction:
Improveprocessing speedVSAvoidmemory management complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system segments database requests into discrete data containers that can be independently managed and transferred. Each data container represents a manageable unit of work that can be allocated to specific computing resources. This segmentation enables faster processing by allowing parallel handling of multiple containers while simplifying memory management through standardized container structures with clear boundaries and ownership.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The container management system acts as an intermediary layer between incoming database requests and the underlying computing resources. It manages the complexity of dynamic container allocation, creation, and transfer operations, shielding higher-level applications from memory management complexities. This intermediary approach enables improved processing speed through efficient container transfer mechanisms while containing memory management complexity within the container management layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10706027B2Database management system with dynamic allocation of database requests
Publication Date: 2020.07.07 SAP SE
  • US10706027B2 patent drawing
  • US10706027B2 patent drawing
  • US10706027B2 patent drawing

AI summary

The invention provides for a database management system (100, 400) comprising a container management system (102). The container management system comprises: a container management system memory (106) for storing machine executable instructions (114) and a container management system processor (104). Execution of the machine executable instructions cause the container management system processor to repeatedly: receive (200) multiple database requests (116) via a first network connection (110), wherein each of the multiple database requests comprises metadata descriptive of the multiple database requests; calculate (202) a receiving rate (118) by counting the multiple database requests received in a predetermined duration; calculate (204) a processor count (120) using a predictive model and the receiving rate; determine (206) a number of data containers (122) using the receiving rate and a container memory model, wherein each of the data containers is a block of the container management system memory assigned by continuous address space; request (208) a processor pool from a processor hosting service (306) via a second network connection (112) to satisfy the processor count; allocate (210) data containers (128, 130, 132, 134) equal to the number of the data containers in the container management system memory; transfer (212) the multiple data base requests to the data containers as they are received, wherein each of the multiple data base requests is assigned to a chosen data container selected from the data containers using the metadata; and transfer (214) a filled data container selected from the number of data containers to the processor hosting service via the second network connection, wherein the filled data container is filled with the multiple data requests above a predetermined threshold.