Zero-Copy Binary Radix Tree for Distributed Key Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed computing environments, maintaining multiple copies of binary keys for key management results in significant memory wastage and performance issues due to the need for each referrer to store entire key copies, leading to increased memory costs and reduced efficiency.

Innovation Solution

Implementing a zero-copy binary radix tree that allows referrers to maintain references to nodes in the tree instead of entire key copies, using a binary radix tree structure to intern binary keys and a reference store for memory-efficient storage of references, enabling efficient key management and reduced memory usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If each referrer maintains a copy of the binary key locally, then key access is straightforward and fast, but memory usage increases significantly due to multiple duplicates

Engineering Contradiction:
Improvekey access speedVSAvoidmemory usage
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent applies the copying principle in reverse - instead of each referrer maintaining a full copy of the binary key, the system creates a compact reference (copy of reference) that points to the shared binary key storage. This reference contains only essential location information rather than the complete key data, thereby reducing memory usage while maintaining fast access through direct reference resolution.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent merges multiple referrer references to the same binary key into a single shared storage location. The binary key is stored once in a common repository, and multiple referrers hold references to this single instance. This consolidation eliminates redundant storage while preserving the ability for any referrer to access the key through their reference.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of operation

If multiple copies of binary keys are maintained across referrers, then each referrer has independent access, but memory costs increase and system efficiency decreases

Engineering Contradiction:
Improveindependent key accessVSAvoidmemory cost
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The system creates compact references that can be independently copied and distributed to multiple referrers without copying the actual binary key data. Each referrer receives a lightweight reference object that independently points to the shared key storage, maintaining independent access capability while minimizing memory consumption.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces an intermediary reference mechanism that mediates between referrers and the actual binary key storage. Instead of direct key copies, referrers interact with the system through references that act as intermediaries, which resolve to the actual key data when needed. This intermediary layer enables independent access while centralizing key storage to reduce memory costs.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If entire binary keys are stored by each referrer, then key management is simple and direct, but performance deteriorates due to increased memory overhead and data duplication

Engineering Contradiction:
Improvekey management complexityVSAvoidsystem performance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments the key management system into two distinct components: (1) compact references held by referrers, and (2) shared binary key storage. This segmentation separates the lightweight access mechanism from the actual data storage, reducing memory overhead while maintaining manageable complexity through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The reference object serves as an intermediary that simplifies key management operations. Instead of managing full binary key copies across multiple referrers, the system manages compact references that automatically resolve to the shared key storage. This intermediary mechanism reduces both memory overhead and operational complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10795865B2System and method for supporting zero-copy binary radix tree in a distributed computing environment
Publication Date: 2020.10.06 ORACLE INT CORP
  • US10795865B2 patent drawing
  • US10795865B2 patent drawing
  • US10795865B2 patent drawing

AI summary

A system and method supports key management in a distributed computing environment such as a distributed data grid. A binary radix tree is used to intern a plurality of binary keys. The binary radix tree is serialized to a byte buffer and a view of the binary is created. A byte sequence interface to the nodes of the serialized binary radix tree allows use of references which refer to positions in the serialized binary radix tree instead of requiring byte array copes of the interned keys. Use of references into the byte array in place of a byte array copies of interned keys reduces the memory overhead associated with referrers such as reverse indices which make reference to values associated with the plurality of binary keys. The reduction in memory overhead enhances performance and capabilities of a distributed computing environment such as a distributed data grid.