Parallelized Database System for High-Volume Data Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems face challenges in efficiently processing large-scale data operations due to limitations in hardware, data storage methods, and restricted co-processing options, leading to suboptimal execution speeds.

Innovation Solution

The implementation of a parallelized database system architecture that includes a parallelized data input sub-system, a parallelized data store, retrieve, and process sub-system, and a parallelized query and response sub-system, which enables distributed processing across multiple computing devices and nodes, optimizing data storage and retrieval operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a traditional database system processes large-scale data operations using single-node architecture, then the system structure remains simple, but the processing speed and productivity are limited

Engineering Contradiction:
Improveprocessing speedVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The database system is divided into multiple independent nodes, each capable of processing data operations independently. The parallelized data input sub-system, parallelized data store, retrieve, and process sub-system, and parallelized query and response sub-system are distributed across multiple nodes, allowing concurrent processing of data operations and significantly improving processing speed while maintaining manageable node-level complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from single-node processing to multi-node distributed processing, adding the dimension of horizontal scalability. By introducing multiple nodes that can process operations in parallel, the system achieves improved productivity without being constrained by single-node hardware limitations

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If hardware resources are increased to improve processing speed, then productivity increases, but the cost and complexity of the system increase

Engineering Contradiction:
Improveexecution speedVSAvoidhardware configuration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Instead of relying on a single powerful node, the system segments computational tasks across multiple standard nodes. Each node handles a portion of the workload, and the parallelized architecture enables efficient distribution of data processing tasks, achieving high productivity without requiring expensive single-node hardware configurations

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple nodes in the system can perform the same functions (data input, storage, retrieval, processing, query execution), providing hardware utilization efficiency. This multi-functionality across nodes allows the system to scale productivity by adding nodes rather than upgrading individual hardware components

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

3Productivity

If data is stored in a centralized manner, then the storage structure is simple, but the retrieval speed and processing efficiency are limited

Engineering Contradiction:
Improvedata retrieval speedVSAvoidstorage architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The centralized data storage is segmented into distributed storage across multiple nodes. The parallelized data store, retrieve, and process sub-system operates on distributed data partitions, allowing concurrent data retrieval operations from different nodes simultaneously, significantly improving retrieval speed while maintaining logical data organization

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system adds the dimension of distributed storage across multiple nodes to the traditional centralized storage model. This enables parallel data retrieval operations and improves scalability, allowing the system to handle larger datasets with faster retrieval speeds without being constrained by single-node storage limitations

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS20250181580A1Estimating energy utilization required to execute an operation via a data lakehouse platform
Publication Date: 2025.06.05 OCIENT HOLDINGS LLC
  • US20250181580A1 patent drawing
  • US20250181580A1 patent drawing
  • US20250181580A1 patent drawing

AI summary

A data storage system is operable to generate an operation energy utilization estimation function based on historic energy utilization data and historic operation execution data. An operation for execution is determined and energy utilization estimation input data is determined for the operation. The operation energy utilization estimation function is performed upon the energy utilization estimation input data to generate energy utilization estimate data for the operation. An energy efficiency strategy for the data storage system is applied based on the energy utilization estimate data generated for the operation.