DATABASE SYSTEM IMPLEMENTATION PRIORITIZATION USING ROBUSTNESS MAPS

• US 20100198808A1
• Filed: 02/02/2009
• Published: 08/05/2010
• Est. Priority Date: 02/02/2009
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Graefe, Goetz, Kuno, Harumi, Wiener, Janet L.
• Application Number:
  US12/364,137
• Publication Number:
  US 20100198808A1
• Time in Patent Office: Days
• US Class Current: 707/713
• CPC Class Codes: G06F 16/24549 Run-time optimisation

Abstract

Computer-implemented systems and associated operating methods take measurements and landmarks associated with robustness maps and perform tests evaluating the robustness of a database engine'"'"'s operator implementations and/or query components. The illustrative computer-implemented system comprises logic that receives one or more robustness maps of measured database system performance acquired during database execution in a predetermined range of runtime conditions and uses information from the robustness map or maps to prioritize potential changes that improve robustness of a database system implementation wherein landmarks in the robustness map or maps are operated upon as a robustness bug describing conditions under which a predetermined implementation of a database operator or query component degrades in a manner different from a predetermined expected manner.

Claims

1. A computer-implemented system comprising:

logic that receives at least one robustness map of measured database system performance acquired during database execution in a predetermined range of runtime conditions and uses information from the at least one robustness map to prioritize potential changes that improve robustness of a database system implementation wherein landmarks in the at least one robustness map are operated upon as a robustness bug describing conditions under which a predetermined implementation of a database operator or query component degrades in a manner different from a predetermined expected manner.

2. The system according to claim 1 further comprising:

logic that prioritizes potential changes to the database system implementation based on severity of individual robustness bugs in terms of amplitude of the degradation, range of condition span for which the robustness bug is present, and frequency with which robustness bug conditions are historically encountered or expected to be encountered.

3. The system according to claim 1 further comprising:

logic that prioritizes potential changes to the database system implementation based on severity of individual robustness bugs in terms of degree to which the degradation can be remedied, estimation of the resources expended to correct the robustness bug, and assessment of risk associated with an action that corrects the robustness bug.

4. The system according to claim 1 further comprising:

a computer that executes the logic.

5. The system according to claim 1 further comprising:

an article of manufacture comprising;

a controller-usable medium having a computer readable program code embodied in a controller for prioritizing potential changes to the database system implementation, the computer readable program code further comprising;

code causing the controller to receive the at least one robustness map of measured database system performance acquired during database execution in a predetermined range of runtime conditions; and

code causing the controller to prioritize potential changes to the database system implementation based on locations and migrations of landmarks on the at least one robustness map.

6. A computer-implemented system comprising:

logic that receives at least one robustness map of measured database system performance acquired during database execution in a predetermined range of runtime conditions and uses the at least one robustness map to identify and prioritize potential changes to a database system implementation and improve robustness with regard to a plurality of conditions including data characteristics.

7. The system according to claim 6 further comprising:

logic that prioritizes potential changes that improve robustness of the database system implementation based on locations and migrations of landmarks on the at least one robustness map.

8. The system according to claim 6 further comprising:

logic that prioritizes potential changes that improve robustness of the database system implementation in terms of degree of robustness exhibited when executing a predetermined database benchmark.

9. The system according to claim 6 further comprising:

logic that analyzes measurements and landmarks in the at least one robustness map, and uses the analysis to prioritize potential changes that improve robustness of a database engine'"'"'s operator implementations.

10. The system according to claim 6 further comprising:

logic that tests performance comprising visualizing location and character of performance changes on the at least one robustness map wherein the at least one robustness map is analyzed to detect circumstances under which performance is sensitive to deviations from expected behavior, identify performance anomalies, and prioritize potential changes that improve robustness of the database system implementation.

11. The system according to claim 6 further comprising:

logic that detects performance degradation by determining curvature between data points on the at least one robustness map comprising identifying locations on the at least one robustness map wherein performance degrades by a predetermined amount or performance degrades in a manner different from a predetermined expected manner, the logic prioritizing potential changes that improve robustness of the database system implementation.

12. The system according to claim 6 further comprising:

logic that uses the at least one robustness map to compare performance of an applied query plan and/or operator to a best known query plan and/or operator, the logic prioritizing potential changes that improve robustness of the database system implementation.

13. The system according to claim 6 further comprising:

logic that uses the at least one robustness map to detect an error condition wherein performance improves as workload increases or operating resources decrease, the logic prioritizing potential changes that correct the error condition of the database system implementation.

14. A computer-implemented method comprising:

prioritizing a database system comprising;

receiving at least one robustness map of measured database system performance acquired during database execution in a predetermined range of runtime conditions; and

using information from the at least one robustness map to prioritize potential changes that improve robustness of a database system implementation wherein landmarks in the at least one robustness map are operated upon as a robustness bug describing conditions under which a predetermined implementation of a database operator or query component degrades in a manner different from a predetermined expected manner.

15. The method according to claim 14 further comprising:

characterizing severity of individual robustness bugs in terms of amplitude of the degradation, range of condition span for which the robustness bug is present, frequency with which robustness bug conditions are historically encountered or expected to be encountered, degree to which the degradation can be remedied, estimation of the resources expended to correct the robustness bug, and assessment of risk associated with an action that corrects the robustness bug; and

prioritizing potential changes to the database system implementation based on severity of the individual robustness bugs.