Database Performance Analysis Using Primary Order Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for performance analysis of requests involving multiple databases and applications are inefficient in calculating the duration of processed requests and identifying performance bottlenecks, as they lack a comprehensive approach to handle diverse database schemas and operations across different applications.
Innovation Solution
A performance test tool (PTT) is implemented to calculate the duration of processed requests by using primary and secondary order identifiers, querying stored duration information across multiple application databases, and analyzing action start and end times to identify performance bottlenecks across CRM, AIA, and BRM applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional performance analysis methods are used for requests involving multiple databases and applications, then the analysis can be performed with existing tools, but the calculation of request duration and identification of performance bottlenecks becomes inefficient and inaccurate
Solution Approach 1:
The patent segments the performance analysis by dividing it into application-level metrics and database-level metrics. It further segments database analysis into schema-level, table-level, and column-level metrics. This hierarchical segmentation allows precise measurement at each level while maintaining overall analysis efficiency through structured data collection and processing.
2Reliability
If comprehensive duration information is collected across multiple application databases, then performance bottlenecks can be accurately identified, but the complexity of querying and processing data from diverse database schemas increases
Solution Approach 1:
The patent creates a universal performance analysis framework that can query and process data from multiple diverse database schemas simultaneously. By defining a common set of performance metrics and a unified query interface that works across different database types (relational, NoSQL, etc.), the system achieves multi-functionality without requiring separate analysis tools for each database type, thus reducing overall complexity while maintaining comprehensive monitoring capability.
3Ease of operation
If detailed action duration and application execution time data are collected, then targeted performance improvements can be identified, but the amount of data to be processed and analyzed increases significantly
Solution Approach 1:
The patent extracts only the most relevant performance metrics from the vast amount of available data. It focuses on extracting key duration information (action duration, application execution time, request duration) and bottleneck identification data, while filtering out redundant information. This selective extraction reduces the data volume that needs to be processed while maintaining the ability to identify performance optimization opportunities.
Data Source
AI summary
A computer-implemented method, a computer program product and a system are provided. The method relates to calculating a duration of an action, wherein the action comprises at least one database operation, wherein the action is one of multiple actions carried out in order to process a request, wherein processing the request includes executing multiple applications, each application having a corresponding application database, wherein the execution of one of the applications includes performing the action on the corresponding application database and storing duration information for the action. The method comprises determining a primary order identifier of the action. Also, the method further comprises querying the stored duration information. The querying comprises specifying a proper subset of attributes of one or more relations, the relations including at least one table, each relation including a plurality of rows. The attributes describe the primary order identifier. The attributes further describing a subset of the duration information including a start time of the action. The querying further comprises specifying conditions that must be met by at least one row of the relations, wherein at least one condition includes attributes of multiple relations. The querying further comprises retrieving, according to the conditions, the specified attributes of the at least one row of the relations. The querying further comprises calculating a duration of the action based on the start time of the action.