Workload-Aware Memory Reclamation in Graph Databases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional memory reclamation strategies in Bw-tree graph databases are inefficient due to high write amplification and failure to consider varying memory reclamation rates across different data segments, as well as the impact of time-to-live (TTL) requirements.

Innovation Solution

Implement a workload-aware memory reclamation process that tracks extent usage characteristics such as update gradients, fragmentation ratios, and TTLs to generate a priority list for memory reclamation, thereby targeting extents with high reclaimable memory and reducing write amplification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional memory reclamation strategies are used in Bw-tree graph databases, then memory space can be reclaimed, but write amplification is high and reclamation efficiency is low

Engineering Contradiction:
Improvememory reclamation efficiencyVSAvoidwrite amplification
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent changes the parameters used for memory reclamation decisions from simple FIFO ordering to workload-aware parameters including update gradients, fragmentation ratios, and TTL requirements. By monitoring these parameters and dynamically selecting extents for reclamation based on their current state, the system achieves higher reclamation efficiency with reduced write amplification.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent implements feedback mechanisms by continuously tracking extent usage characteristics such as update gradients and fragmentation ratios. This feedback information is used to dynamically adjust the memory reclamation strategy, selecting extents that are most suitable for reclamation at any given time, thereby improving efficiency and reducing unnecessary write operations.

Inventive Principle:
Principle #23Feedback

2Productivity

If memory reclamation is performed without considering extent usage characteristics, then reclamation process is simple, but reclamation rate varies inefficiently across different data segments

Engineering Contradiction:
Improvememory reclamation rateVSAvoidreclamation process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the graph database storage into multiple extents and applies different reclamation strategies to each extent based on its specific usage characteristics. By tracking and analyzing individual extent properties such as update gradients and fragmentation ratios, the system can optimize reclamation rates for each segment independently, leading to overall improved efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by making reclamation decisions based on the specific characteristics of each extent rather than treating all storage uniformly. Each extent is evaluated individually using metrics like update gradients and fragmentation ratios, allowing the system to apply reclamation where it is most beneficial while avoiding unnecessary operations in other regions.

Inventive Principle:
Principle #3Local quality

3Reliability

If TTL requirements are not considered in memory reclamation, then reclamation process is faster, but data validity and TTL compliance are compromised

Engineering Contradiction:
ImproveTTL complianceVSAvoidreclamation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-tracking TTL information and extent usage characteristics before reclamation is needed. This advance preparation allows the system to quickly identify suitable extents for reclamation that meet TTL requirements, avoiding time-consuming checks during the actual reclamation process while ensuring data validity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250103204A1Workload-aware memory reclamation on graph databases
Publication Date: 2025.03.27 LEMON INC(GB)
  • US20250103204A1 patent drawing
  • US20250103204A1 patent drawing
  • US20250103204A1 patent drawing

AI summary

Implementations for performing workload-aware space reclamation are provided. One example includes a computing system comprising: processing circuitry and memory storing instructions that, during execution, causes the processing circuitry to: track extent usage characteristics for each of a plurality of extents storing data for a graph database; and perform memory reclamation to reclaim storage areas corresponding to invalid data, wherein performing the memory reclamation comprises: generating a list of extents to be reclaimed based on the tracked extent usage characteristics; and reclaiming memory space on the plurality of extents in order based on the list of extents.