Plotting Data Distribution Architecture for Client Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional computer data systems face challenges in efficiently synchronizing dynamically changing plotting data across multiple clients, leading to high memory usage, reduced responsiveness, and increased communication with servers, while also lacking local modification capabilities to enhance user interactions.

Innovation Solution

A computer database system with remote query processors that generate a plotting data structure, transmit initial snapshots, and subscribe clients to receive updates, allowing local replica creation and asynchronous updates to plots without server contact, enabling efficient data synchronization and parallel processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If clients access tables from data sources to create visualizations, then plotting functionality is provided, but memory usage increases and synchronization efficiency decreases

Engineering Contradiction:

Improveplotting processing efficiencyVSAvoidmemory usage

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The system segments plotting processing by creating separate plotting data structures that are independent from the original data sources. Each client receives a dedicated plotting data structure with export object handles, allowing independent manipulation and reducing memory pressure on individual clients while maintaining efficient plotting processing.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system creates copies of data through export object handles that reference portions of original objects. Instead of clients directly accessing and storing complete data sources, the system transmits plotting data structures with handles to specific data portions, reducing memory usage while enabling efficient plotting operations.

Inventive Principle:

Principle #26Copying

2Reliability

If clients continuously query servers for plot updates, then data synchronization is maintained, but communication overhead increases and responsiveness decreases

Engineering Contradiction:

Improvedata synchronization consistencyVSAvoidcommunication time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by transmitting initial snapshots of data along with plotting data structures before the client needs to display plots. This allows clients to have ready-to-use data without continuous querying, reducing communication time while maintaining synchronization through update propagation graphs.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms through update propagation graphs that automatically notify clients of data changes. When data in data sources changes, the system propagates updates through dependent plotting data structures, ensuring clients receive necessary updates without continuous polling, thus reducing communication overhead while maintaining consistency.

Inventive Principle:

Principle #23Feedback

3Measurement precision

If clients access original data sources directly, then data accuracy is maintained, but local modification capability is lost and server communication is required

Engineering Contradiction:

Improvedata accuracyVSAvoidlocal modification capability

Core Design Contradiction:

Measurement precisionVSEase of operation

Solution Approach 1:

The system creates local copies of data through plotting data structures with export object handles. These handles reference specific portions of original data sources, allowing clients to work with local copies for modifications while maintaining accuracy through the handle references that point to the original accurate data.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system introduces plotting data structures with export object handles as intermediaries between clients and original data sources. These intermediaries allow clients to perform local modifications on copies while the handles maintain connections to the original accurate data, enabling both local operation and data accuracy.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If the system maintains full data copies for each client, then data availability is improved, but memory consumption increases and scalability is reduced

Engineering Contradiction:

Improvedata availabilityVSAvoidsystem scalability

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments data into original data sources and client-specific plotting data structures. Instead of maintaining full data copies for each client, the system creates segmented plotting data structures with export object handles that reference portions of shared data sources, reducing memory consumption while maintaining data availability and improving scalability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system creates universal plotting data structures that can serve multiple clients simultaneously. The export object handles and plotting data structures are designed to be shared and referenced by multiple clients, reducing the need for duplicate data copies while maintaining data availability for all clients.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20240232262A1Computer data distributing architecture for efficient distribution and synchronization of plotting processing and data

Publication Date: 2024.07.11 DEEPHAVEN DATA LABS LLC

AI summary

Described are methods, systems and computer readable media for computer data distribution architecture for efficient distribution and synchronization of plotting processing and data.