Database Resharding Using Weighted Workload-Based Instance Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database resharding techniques based on size do not result in an even split of workload, as they do not account for the varying impacts of input/output operations, leading to inefficient resource utilization.

Innovation Solution

Analyze read and write operations in database instances and apply weighted sums to select instances for resharding, ensuring an even split in workload by grouping them based on computed metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If database instances are selected for resharding based on size, then the resharding process is simple to implement, but the workload is not evenly distributed across servers

Engineering Contradiction:
Improvesimplicity of resharding implementationVSAvoidworkload distribution efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent changes the selection parameter from database size to workload metrics (read operations, write operations, connections). By computing a weighted sum of these metrics, the system selects database instances based on actual workload contribution rather than size, achieving even workload distribution while maintaining a systematic selection process

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent replaces the simple size-based mechanical selection with a computational approach using weighted sums of workload metrics. This substitution allows the system to account for the varying impacts of different operations (reads, writes, connections) on server workload, achieving better load balancing

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If database instances are selected for resharding based on workload metrics with weighted sums, then even workload distribution is achieved, but the selection process becomes more complex

Engineering Contradiction:
Improveworkload distribution efficiencyVSAvoidcomplexity of resharding selection process
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces weighted parameters for different workload metrics (read operations, write operations, connections) to capture their varying impacts on server load. By changing from a single parameter (size) to multiple weighted parameters, the system achieves accurate workload-based selection while maintaining a systematic and automated process

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system automatically computes workload metrics and weighted sums to select database instances for resharding, eliminating the need for manual analysis. The automated computation of metrics and the systematic selection process reduce operational complexity despite the increased analytical depth

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250371033A1Workload inspired input selection of databases for resharding
Publication Date: 2025.12.04 RUBRIK INC
  • US20250371033A1 patent drawing
  • US20250371033A1 patent drawing
  • US20250371033A1 patent drawing

AI summary

Methods, systems, and devices for data management are described. A database server may identify workload metrics for a set of database instances and generate a weighted sum of the workload metrics for each database distance. The database server may select, for a resharding operation, a first set of database instances and a second set of database instances, and the selection may be based on a relationship between a first sum of one or more respective weighted sums for the database instances in the first set and a second sum of one or more respective weighted sums for the database instances in the second set. The database server may execute the resharding operation that results in the first set continuing to be supported by the first database server and the second set being supported by the second database server.