Query Plan Robustness Mapping for Database Performance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database systems face performance degradation due to the disparity between expected and actual runtime conditions, particularly when multiple queries execute simultaneously, leading to unexpected performance issues as data skew and resource availability vary significantly, causing selected query plans to be suboptimal under adverse conditions.

Innovation Solution

A computer-implemented system evaluates the robustness of query plans by measuring performance across a range of runtime conditions, producing maps that compare the selected plan to alternative plans, identifying landmarks where performance degrades, and analyzing these maps to predict and analyze performance continuity under varying conditions, thereby enabling the selection of more robust query execution plans.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a query optimizer selects a query plan based on estimated cost and expected runtime conditions, then the plan appears optimal under expected conditions, but performance degrades unexpectedly when actual runtime conditions differ from estimates

Engineering Contradiction:
Improvequery plan performance reliabilityVSAvoidquery execution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary evaluation of query plans across a predetermined range of runtime conditions before actual query execution. By pre-measuring performance under various conditions and creating robustness maps, the system prepares advance knowledge about plan behavior that can be used during actual execution without requiring re-evaluation at runtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from measuring query plan performance across different runtime conditions to create robustness maps. These maps capture the relationship between runtime conditions and performance outcomes, providing feedback information that helps the query optimizer make more reliable plan selections by understanding how plans behave under varying conditions rather than relying solely on static cost estimates.

Inventive Principle:
Principle #23Feedback

2Productivity

If the query optimizer examines all possible query plans to find the most efficient one, then the selected plan is optimal under expected conditions, but the search space becomes very large due to query complexity

Engineering Contradiction:
Improvequery execution efficiencyVSAvoidquery plan search space complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary measurements of query plan performance across a predetermined range of runtime conditions before actual query execution. By pre-evaluating plans under various conditions and storing the results in robustness maps, the system eliminates the need to re-examine all possible plans during actual execution, significantly reducing the effective search space while maintaining optimality.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates virtual copies of query plans evaluated under different runtime conditions by measuring performance across predetermined conditions and storing results in robustness maps. These copies allow the system to understand plan behavior under various conditions without actually executing all possible plans, reducing the effective search space while maintaining comprehensive performance knowledge.

Inventive Principle:
Principle #26Copying

3Reliability

If the system measures query plan performance across a wide range of runtime conditions, then the robustness map provides comprehensive performance insight, but the measurement and analysis process becomes more complex

Engineering Contradiction:
Improveperformance prediction accuracyVSAvoidperformance evaluation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the runtime condition space into a predetermined range of conditions that are systematically measured. By dividing the complex continuous space of runtime conditions into discrete, manageable segments (such as different data cardinalities, resource availability levels, etc.), the system can comprehensively measure performance without creating an unmanageably complex evaluation process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary measurements of query plan performance across different runtime conditions before actual query execution. By pre-evaluating plans under various conditions and storing the results in robustness maps, the system prepares advance performance data that can be queried during actual execution, eliminating the need for complex real-time analysis while maintaining comprehensive performance insight.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9128984B2Query plan analysis of alternative plans using robustness mapping
Publication Date: 2015.09.08 MICRO FOCUS LLC
  • US9128984B2 patent drawing
  • US9128984B2 patent drawing
  • US9128984B2 patent drawing

AI summary

Computer-implemented and associated operating methods evaluate robustness of a query plan by measuring performance with regard to a range of runtime conditions and producing a map of relative performance of the given query plan when compared with alternative plans for a range of conditions. The computer-implemented system comprises logic that evaluates the selected query plan in comparison to multiple alternative query plans in a predetermined range of runtime conditions that include data characteristics. The logic produces a set of performance measurements and analyzes the measured performance to map performance of the selected query plan in comparison to performance of one or more alternative query plans.