Database Performance Testing for Realistic Sharded Query Loads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database performance testing methods fail to simulate realistic load behavior and provide accurate indications of future performance, especially in complex database configurations such as sharded and multi-tenanted systems, leading to potential unexpected load issues.

Innovation Solution

A method and system for conducting performance tests on databases that involve receiving configuration options, retrieving organization data, performing query operations based on these options, and recording performance data, including the use of stress and scheduled runners to simulate various query frequencies and loads, with features like thread sleeping and backlog management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If existing performance testing solutions are used on complex database architectures (sharded, multi-tenant), then the testing can be conducted, but the load behavior becomes non-realistic and performance indications are poor

Engineering Contradiction:
Improveperformance test accuracyVSAvoidload behavior realism
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The system performs preliminary actions by retrieving organization data and understanding real query patterns before conducting performance tests. This allows the test to simulate realistic user behavior and load conditions rather than using artificial or non-realistic load patterns, thereby improving both measurement precision and reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of real user behavior patterns by analyzing organization data and query logs. Instead of using generic or non-realistic load patterns, it replicates actual user interactions, query frequencies, and data access patterns to achieve realistic load behavior that accurately reflects production conditions

Inventive Principle:
Principle #26Copying

2Productivity

If the database is sharded across multiple servers to handle larger data volumes, then scalability is improved, but query latency increases due to the need to search multiple shards

Engineering Contradiction:
Improvedatabase scalabilityVSAvoidquery latency
Core Design Contradiction:
ProductivityVSSpeed

Solution Approach 1:

The system acknowledges the segmented nature of sharded databases and adapts its testing approach accordingly. By retrieving organization data and understanding data distribution across shards, it can simulate queries that realistically traverse multiple shards, thereby measuring both scalability benefits and latency costs accurately

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements periodic query operations at configured frequencies to simulate real-world usage patterns. This periodic execution across multiple shards allows measurement of latency under realistic conditions while maintaining scalability, as the timing and frequency reflect actual user behavior rather than continuous or artificial load

Inventive Principle:
Principle #19Periodic action

3Productivity

If multi-tenanted database architecture is used to serve multiple organizations, then resource utilization is improved, but query performance may degrade due to contention from other tenants

Engineering Contradiction:
Improveresource utilizationVSAvoidquery performance consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system copies real multi-tenant interaction patterns by retrieving organization data and simulating queries from multiple tenants concurrently. This allows accurate measurement of performance consistency under realistic contention conditions, reflecting how multiple organizations actually share database resources

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary retrieval of organization data to understand the multi-tenant structure and data distribution before executing performance tests. This enables realistic simulation of tenant-specific queries and inter-tenant contention scenarios, improving reliability of performance measurements

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260111329A1Methods, Systems and Computer-Readable Media for Testing Database Performance
Publication Date: 2026.04.23 XERO
  • US20260111329A1 patent drawing
  • US20260111329A1 patent drawing
  • US20260111329A1 patent drawing

AI summary

A method for conducting a performance test on a database system comprises receiving a plurality of configuration options. The configuration options determine parameters of the performance test to be conducted. The method further comprises retrieving organisation data from the database system to be tested, and performing a plurality of query operations on the database system. The plurality of query operations are based at least in part on the plurality of configuration options and the retrieved organisation data. The method further comprises recording database performance data based on the performance of the performed query operations.